Jacqueline,
I tried this, but to no avail:
>have you tried seting the defaultstack to the one
>with the selection?
Robert,
I did have something like this in mind as my workaround. I managed to save the
selectedChunk, field and stacks into the other stack, and then use these to
reconstruct the s
Thanks for the suggestion. It was a "mouseUp" handler, so I changed it to
"mouseDown" but it didn't make any difference.
I think the issue is actually to do with moving from stack to stack: the
selectedChunk only refers to the character numbers in a (numbered)
field. There
is no reference to a
Bernard Devlin <[EMAIL PROTECTED]> wrote:
I think the issue is actually to do with moving from stack to stack: the
selectedChunk only refers to the character numbers in a (numbered) field. There
is no reference to a stack. So it seems logical to me that if one is to click
on another stack, tha
Thanks for the suggestion. It was a "mouseUp" handler, so I changed it to
"mouseDown" but it didn't make any difference.
I think the issue is actually to do with moving from stack to stack: the
selectedChunk only refers to the character numbers in a (numbered) field. There
is no reference to a
I'm still trying to solve the problem of passing the field reference of the
insertion point to my palette so that I can insert the label of a palette button
into the field. (All the buttons and groups of the palette have "traversal on is
false"). I still don't understand why the selectedChunk belo
Thanks for the pointers Ken and Jeanne.
Here's what I've found.
If there is actually some selected text in the field with the insertion point,
then the label of the button can be inserted after the text (using "after the
selectedChunk"). However, if I intercept the processing of the handler in t
Thanks for jumping in Jeanne. You're right that the objects referenced on
Stack B are buttons.
I've "set the traversalOn of the templateButton to false" prior to the creation
of the buttons, but still when I have the insertion point in Stack T and click
on a button, the "onMouseup" of the button
At 7:31 PM -0800 12/6/02, Bernard Devlin wrote:
>I have two stacks. Stack T contains text fields, and Stack B contains
>buttons.
>
>Whilst typing in Stack T, if the user requires input from Stack B I want the
>user to be able to just click on an item in Stack B, and have the text
>associated with
I have two stacks. Stack T contains text fields, and Stack B contains buttons.
Whilst typing in Stack T, if the user requires input from Stack B I want the
user to be able to just click on an item in Stack B, and have the text
associated with the clicked button inserted at the place in the field
