"Al Hospers" <[EMAIL PROTECTED]> wrote
> so a slider function should only be passing the current slider knob
> location as a % of the slide. thus it could be used for anything that
> would use a slider, not just QT! OK, that's good.
Perhaps not even a percentage. When the slider 'registers' to be a
view/controller for an integer range in another object, it might also store
the maximum (and minimum) values that it is going to represent. Internally,
it might store that as a percentage, or more likely as a fraction of its
entire width.
> 1 - so how would a slider behavior know what object to talk to? would
> you enter the global reference to the QTObject in the
> getObjectProperties dialog?
This is a good question.
Well, I'm certainly thinking about both of these objects as behaviors. I
would have the QT wrapper behavior with a parameter dialog where you might
enter message symbols for 'setup' (or whatever) and 'update' (or whatever)
and a target sprite to send them to.
The slider would have similar fields in its parameter dialog, so that if
someone drags the slider, it can inform the object whose integer range it
represents of the change.
There are certainly other ways to do this.
I'd also agree with Jakob that this is example is probably to simple to be a
really useful test of these approaches. As ususal, we'd rather need to pick
a really complex task, and then it would seem too much like work. :)
--
_____________
Brennan
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
