Notepad
a maxscript that serves as a kind of notepad within 3ds max. the user can save little but maybe important information that are file related, for example special settings or infos for team members. whenever a file is opened which contains custom notes the notepad-window will pop up automatically on startup (script must be placed in scripts/startup folder).
- the script works fine with max9-32, max2009-64 and max2011-64
- it is recommended the script is placed in the "Scripts/Startup" folder
- also you can bind a button or a hotkey to it
- the notepad will only work if you have at least one object in the scene!
Attachment | Size |
---|---|
notepad_101.ms | 5.35 KB |
Comments
Sorry Nik, I didn't realize
Sorry Nik, I didn't realize your comment was aimed at ikerclon. I thought you meant the notepad script...it's been a long day:)
Use standard tools - it's not
Use standard tools - it's not stupid
What is written in the script pad no one but you will not read
Don't be silly
Don't be silly
Easier use maxtext spline
)
Nice script!
I was thinking about writing a little tool to assist me when saving the different versions of my work, when I did a search and found this. It's very useful, so thanks for sharing :)
However, my idea was aiming in using 'Summary Info' to store these notes so the clients do not have to install anything. I remember you could call these 'comments' from the Windows Explorer some years ago, but I can't do it on Windows 7. That's weird...
Good job!!!
INI file could help
Well, if you intend to be a single text file for an entire folder, its looks to me w'd be most easy to use INI file. You can create separate section for each max file using it name. Something like:
All what w'd need is just a simple dialog with edittext.
If you hit some difficulty to write such a script alone, just mail me ;)
Anubis
my recent MAXScripts RSS (archive here)
Yes, the problem with that is
Yes, the problem with that is if you have a few hundred revisions of a file, looking through the properties of each file to find that specific comment you are looking for can take forever. If there was one text document that contained all the notes, you can open the .txt and search for whatever string you want to quickly find the file. I used file properties for a while but its just too chaotic on large jobs.
RE: "If the user decided to
RE: "If the user decided to make a note in the summary portion of the file..."
Hi Gerald,
If you like this solution you can search in the help for fileProperties struct, but its
not safety
. They can be deleted, become blank, and who knows why but no eny warning about in the help.RE: "i would love a real window resize but i believe i can not realisize it..."
Hi le1setreter,
try resized event (
on <Rollout> resized <Point2> do
).[EDIT] @Gerald - you post at the same time as me, and as reading it, I guess you probably need database management.
Regards,
Anubis
my recent MAXScripts RSS (archive here)
Hey le1 setreter, Perpahs I
Hey le1 setreter,
Perpahs I was a little too vague in my description. I meant sort of a single text file per version of the scene file that would sit in the same folder. Like, if I had CAR_BEAUTY_v001, CAR_BEAUTY_v002, CAR_BEAUTY_v003, etc, maybe a single text file (maybe CAR_BEAUTY_vXXX.txt ??) that would have the version history of all those files. If there is another render pass in the same folder like ENV_FOREGROUND_v001 or FUMES_v001, a new text file could be created in the same folder summing up the version history of each respective file. If that seems like a bit of work, (I realize you are kind enough to create this out of your own good will) perhaps one text file for the entire folder which might look like this....
CAR_BEAUTY_v001 - model broken up into render passes
CAR_BEAUTY_v002 - wheel position moved (20 degree rotation)
CAR_BEAUTY_v003 - hierarchy reorganized with DUMMY_A as parent
ENV_FOREGROUND_v003 - added meshsmooth detail close to camera
FUMES_v003 - reduced size of simulation area
great work on the script so far though. If you are abale to add something of this nature in the near future, i'll surely be using it in my pipeline.
thank you all for your
thank you all for your feedback.
looks like the windowsize is still something that has to be improved. i would love a real window resize but i believe i can not realisize it (maybe dotnet functions could do but i am not sure ...).
so i will go the easy way and add some more different sizes.
also the point with the txt-files mentioned by gerald abraham sounds interesting. although when starting the script my main intention has been to work absolut internal the scene and so to avoid external txt-files i think it won't be a big problem to add some check-button for additional exporting the notes as txt-files. ....but, questionable here is to create one note for each scene or each scene folder. maybe i should add another options like "project-related" or "file-related"...
i will think about it and start some upadating as soon as i find a little bit more time. in the meantime any ideas/suggestions are always appreciated.
thanks
-le1setreter