I am using dynamic access api's and would want to create a window, "create"
in the sense that it is a template to be used in Rb with the "new" operator
or in the plugin with "REALnewInstance".
I am able to instantiate a window in runtime by calling
REALnewInstance("Window");
and can set certain properties like the window rect, but fail to be able to
set the composite and frame = 9 (metal). These failures are understandable,
because the window is created at runtime with REALnewInstance. I would like
to set the properties first, and then call REALnewInstance.
There might be a workaround if RB would allow "REALnewInstance" to work with
a custom name like "Window1". Unfortunately,
REALnewInstance("Window1"):
leads to a nil object. Calling "new window1" in rb and feeding the instance
to the plugin will allow manipulation of the window by the plugin, however,
it defies the purpose of the plugin.
I thought about the keyword "class" in rb, which might be the equivalent of
"REALclassRef" of the plugin api. However, defining a method in the plugin,
like
"doSomething(xwin as class)"
leads to the premature exiting of rb during loading of the plugin. RB reads
it as an invalid plugin format. For your info, defining
dim xwin as class
appears to be legal in rb, while I am ignorant about usage of this keyword
"class" in rb.
Any suggestions?
Alfred
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://www.realsoftware.com/listarchives/lists.html>
|