[request] hold-fetch (3ds Max like) feature
-
@rv1974 said:
Doable?
Only way I can see this be done via Ruby is by saving a copy of the model when you mark your point. And then just open the model representing your state.
@rv1974 said:
Important: it must respect the memory buffer.
Not sure what you mean by this... ? You mean it should keep the different states in memory? That'd require some all too low-lever programming than what you can do with the Ruby API.
-
@thomthom said:
@rv1974 said:
Doable?
Only way I can see this be done via Ruby is by saving a copy of the model when you mark your point. And then just open the model representing your state.
@rv1974 said:
Important: it must respect the memory buffer.
Not sure what you mean by this... ? You mean it should keep the different states in memory? That'd require some all too low-lever programming than what you can do with the Ruby API.
- Doesn't it mean long times to open a reverted version of file? It would't be good.
- By respecting the memory buffer I mean ability to paste things "from the future". See my example.
(a.mark the file state-> b.produce something -> c. copy-> fetch to the marked point-> d. paste this "something")
-
@rv1974 said:
By respecting the memory buffer I mean ability to paste things "from the future". See my example.
That is always "respected" (i.e. the system clipboard cannot be overridden from the application unless you copy something else onto it).
I also often use this method. Make a complex intersection for instance and instead of painstakingly removing all the leftover, I copy what I need, go back a couple of steps, remove the original (bigger chunks) instead and paste in place...
-
@gaieus said:
@rv1974 said:
By respecting the memory buffer I mean ability to paste things "from the future". See my example.
That is always "respected" (i.e. the system clipboard cannot be overridden from the application unless you copy something else onto it).
I also often use this method. Make a complex intersection for instance and instead of painstakingly removing all the leftover, I copy what I need, go back a couple of steps, remove the original (bigger chunks) instead and paste in place...
That is always "respected" in Sketchup itself. I just wasn't sure how a plugin author would treat a copy-paste function.
-
The Ruby API gives no access to the clipboard. Even if it did, there'd be no way to prevent the user from copying something else into the cplitboard. Nor can one put multiple items into the clipboard.
This is far from a trivial thing. I don't see any way one can copy a model into memory via SketchUp Ruby API.
-
If you make component from some of your geometry and right-click on it, you will see that you can save it separately from your model. So, if you save parts of your work in a temporary place, you can then insert them as components (then explode, if you need raw geometry) in any moment of your modelling process. It's like multiple items saved in clipboard, but without clipboard
. -
In terms of 'marking' the SKP's state... the nearest is perhaps my 'Archiver' tool that saves a snapshot of the SKP at that very instant you 'Archive' it [into an Archives folder with the SKP]. Its name is user+date+time stamped. As you continue modeling the two will diverge... To revert to an Archived version you must manually open the Archived version - of course you can then choose to overwrite the original SKP using a 'save_as'...
You could 'emulate' the clipboard by exporting the selection or whole model to a user+date+time stamped named SKP in say a 'Clipped' folder with the SKP... OR even by making a Component of your Selection inside the SKP itself - leaving the original selection unchanged - that way you can see its contents in its icon...
However, I'm still not clear how it is intended to use the tool 'in anger'... Perhaps a little more narrative description would help - leaving us to think how the magic gets done behind the scenes... -
I think it sounds like the snapshot feature in Photoshop. So regardless if you press save you'll be able to revert back to the snapshot status if needed. This would nullify the ctrl-zing as such. As my workflow is erratic as it is I'd more than likely forget to snapshot.
But TIG's Archiver is a good alternative as suggested by the machine him/herself?
-
@tig said:
In terms of 'marking' the SKP's state... the nearest is perhaps my 'Archiver' tool that saves a snapshot of the SKP at that very instant you 'Archive' it [into an Archives folder with the SKP]. Its name is user+date+time stamped. As you continue modeling the two will diverge... To revert to an Archived version you must manually open the Archived version - of course you can then choose to overwrite the original SKP using a 'save_as'...
You could 'emulate' the clipboard by exporting the selection or whole model to a user+date+time stamped named SKP in say a 'Clipped' folder with the SKP... OR even by making a Component of your Selection inside the SKP itself - leaving the original selection unchanged - that way you can see its contents in its icon...
However, I'm still not clear how it is intended to use the tool 'in anger'... Perhaps a little more narrative description would help - leaving us to think how the magic gets done behind the scenes...
Basicly my request is very similar to your Archiver (I love it BWT and use it for backup purposes basically) but it'd workinstantlyand within the same working session (no external file to be saved\reopen). 'Hold\fetch' in 3ds Max and 'snapshot' in Pshop both work in a flash.
-
Instantly is impossible. Even Copy+Paste takes time depending on how much you copied.
Advertisement