Hi,
Is there allready talked about how to select the primitives an engine
should render?
Could we add a “render selected atoms” (+ “render all atoms”) butten
to the engine widget (e.g. in the configuration tab) which would call
Engine::setPrimitives() for the currently selected engine and pass the
current selection as argument. This would allow the allready present
code for selecting primitives (selection tool, selectextension) to be
reused. New options to the selectextension could be used without
additional code. The same is true for when we have scripting support.
Finally, this would make it for the user easy to select which engine
render which atoms.
Tim
On Feb 5, 2008, at 5:10 PM, Tim Vandermeersch wrote:
Is there allready talked about how to select the primitives an engine
should render?
Could we add a “render selected atoms” (+ “render all atoms”) butten
to the engine widget (e.g. in the configuration tab) which would call
Engine::setPrimitives() for the currently selected engine and pass the
current selection as argument. This would allow the allready present
code for selecting primitives (selection tool, selectextension) to be
reused. New options to the selectextension could be used without
additional code. The same is true for when we have scripting support.
Finally, this would make it for the user easy to select which engine
render which atoms.
Geoff and I were talking about this and I am certainly very much in
favour of this functionality being added in. The UI may need tweaking
as we need to be careful to keep things intuitive but this would make
typical use cases much more intuitive.
I would be glad to look over what you do after you committed it and
see if I can help to tweak it. I am still trying to get this surface
stuff working and trying to keep focussed on this right now…
Thanks,
Marcus