On Aug 1, 2005, at 2:06 PM, Ken Ray wrote:
I'm curious... why won't "copy group" solve your problem? That's
currently
the Rev-native way to do this kind of stuff (unless I'm not
understanding
correctly what you're trying to do).
It probably will. It just doesn't feel as tidy as if I could put it,
with the rest of the data I need to send to the dialog, into a custom
property. Anything with two stages constitutes a strain on my brain :).
(The situation, if you're curious, is this: I have a dozen or so
"Additional Exercises" cards in a stack which is a tutorial on
scanning metrical verse. Each card displays a poem, which is image
that began as as a screenshot; over each line of the poem is an
opague borderless field hiding the scansion marks above the line, and
a transparent borderless button. When the user clicks the button, a
complicated dialog box will come up. It will show a [screenshot of
the] line, with individual "hiding" fields over each of its scansion
marks. The user will click on syllables that are stressed, and the
stress marks will appear. When that's done, the user will click a Go
On to get to another card, in which the same line is shown, now with
stress and slack marks revealed over every syllable, but the foot-
division marks still hidden; below that, a set of check boxes, one
per foot, and a set of radio buttons with the names of possible feet.
Data in a custom property in the poem's card will list the feet for
each line, and possibly the number of stressed syllables. My idea was
to send to the dialog, when the user calls it up by clicking on any
line, a packet of data giving the "correct" answers to the foot
questions; but the dialog also needs, as data, the [screenshot of
the] line and its marks, and the little fields that hide the marks
until the right mouse clicks. I guess I can just send the dialog
those two different kinds of data in two operations -- it just
doesn't feel quite as efficient as sending it all at once. It means
that a copy of each line's screenshot, in a group with all its little
hiding fields, needs to be stored somewhere elese -- most simply, I
guess, invisibly on the card itself. Hope any of this makes any
sense. I'm not sure it does to me, any more.)
Charles
_______________________________________________
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
