Show messages: All
1-3
4-6
From: pressure (PEER)
Hi OSTexo,
Attached is a script called HideMem that I use in place of the native Hide. It keeps a memory of what was hidden last and if it's run again with nothing selected it will un-hide the most recently hidden stuff. The isolate part of it also works a little differently to allow drilling into nested groups.
I like your idea of storing the full history of hide operations so that they can be undone sequentially. This script could be modified to do that, though I don't have time to tackle that at the moment. One problem with this script is that it runs slowly in heavy scenes; especially those with a lot of nested groups.
Install by going to MoI's appdata folder.
On Windows you can find the MoI appdata folder by typing Win+R to bring up the Windows "Run" dialog and then type in:
%AppData%\Moi\
On Mac from a Finder window, go to the menu and pick Go > "Go to folder" and type in:
~/Library/Application Support/Moi/
You should see the folders “commands”, "startup", and "scripts". Put HideMem.htm and HideMem.js in
scripts.
To set up shortcut keys go to Options > Shortcut Keys and paste in each of following three lines as a separate key:
code:
HideMem
script:/* view hidden objects */moi.command.setOption('HideMem', 'ctrl'); moi.command.execCommand('HideMem');
script:/* isolate */moi.command.setOption('HideMem', 'rmb'); moi.command.execCommand('HideMem');
To replace the native Hide button with this version put EditTabContent_customizer.js in the startup folder.
- Peer
Attachments:
HideMem.zip
From: Michael Gibson
Hi OSTexo,
For this part:
> Yes, I'd like to be able to select a surface and toggle lock it via keyboard shortcut.
You can make a keyboard shortcut that does the same as pushing the Edit > Lock button by putting in this for the "Command" part of the shortcut key:
script: moi.geometryDatabase.lock();
- Michael
From: OSTexo
Hello,
Thanks for the info pressure. Unfortunately the models I'm working with can be fairly heavy at the start as I begin defeaturing and stripping off the details to build them back up or organize them to pass along to others so they can do their work.
Session history on tools like lock and hide would be nice, I'm not in either camp when it comes to parametric vs. direct modeling, I think trying to force those two methods together is a mistake. There is a third option that can be built that really mimics how many humans learn to design physical products intuitively. I use version control systems, but having one designed into a product kind of squashes the debate on which method is "better". I'm doing it in MoI already, but it's manual and clunky. I like the idea of being able to take quick model snapshots and to save those onto layers while moving back and forth on those layers easily to see the structure and branches of the model tree. That way I can have milestones throughout the model and even copy branches off the model to send to others while preserving file compatibility for everyone. I don't care much about saving history outside the current session, that's what the snapshotting to layer is for.
Michael, thanks for the script for locking, it'll help me in process.
Show messages: All
1-3
4-6