Hi Len,
I make new objects all the time. I just combine the components in a
group and when I need it, I copy the group, by script, from a
template stack to its destination. Setprop handlers allow me to treat
the group as if it were a true, native object.
Best,
Mark
--
Economy-x-Talk
Consultancy and Software Engineering
http://economy-x-talk.com
http://www.salery.biz
Get your store on-line within minutes with Salery Web Store software.
Download at http://www.salery.biz
Op 19-mrt-2008, om 14:02 heeft Len Morgan het volgende geschreven:
Putting the OOP vs rOOP discussion aside for a moment, I would love
to have the ability to create "new" GUI objects. For example,
consider a fader for a mixing board.
It has a sliding "thumb" (like a scrollbar), usually a pan control
at the top, perhaps a VU meter next to the slider to show the
signal (sort of a progress bar), and a couple of text fields at the
bottom for the name of the channel (Guitar, Vocal, etc), and the
current dB value of the slider. Such an object would have
properties for current slider position, set the VU meter level, set
the pan position, etc. I'd like to be able to create this object
and place it on a card just like a button or field.
I suppose this could be done with a group (just about all of the
required pieces are there and could be manipulated with xTalk) but
I don't know of an easy way to store that "object" in such a way
that I could drop it on to a card. Perhaps a future enhancement
might be "stack format" that could save just an object in it (.obj
or .wid?). I don't think that would be too big a stretch.
Any ideas or comments?
len morgan
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
