2009-02-11 02:55 AM
2009-09-02 01:18 PM
2009-09-02 01:58 PM
Karl wrote:Karl, Here's my source -Peter wrote:Curious where you saw that phrase? Link?
Library parts will be able to create their own MVOs
Thanks,
Karl
2009-09-02 02:30 PM
2009-09-02 02:38 PM
2009-09-02 02:55 PM
2009-09-02 03:05 PM
Peter wrote:I don't think that this new feature will be able to do that.
Does this mean that library parts will be able to access and be controlled by the standard MVOs as well?
For example, the question at the start of the thread - can you program a beam object to behave according to the beam specific MVOs?
I guess you could create your own separate controlling parameter, but I would hope that the existing MVO parameter would be able to control all 'beams' in AC13.
2009-09-02 03:36 PM
laszlonagy wrote:aaaargh! When will they ever finish something properly!!??Peter wrote:I don't think that this new feature will be able to do that.
Does this mean that library parts will be able to access and be controlled by the standard MVOs as well?
... can you program a beam object to behave according to the beam specific MVOs?
The way these kind of things usually work is that new GDL Global Variables are introduced which GDL Scripts can read and act accordingly.
But I do not see any such new GDL Global which would enable to read states of already existing MVO settings.
Would be nice though.
I said this before that in my opinion GDL should be able to inquire a lot more about the state of the Project, including all MVO settings and all Project Preferences.
2009-09-02 08:36 PM
2009-09-03 12:48 PM