What I have done is put an "on mouseenter" handler in the palette buttons (or
at a higher level, in the palette card script) that saves the current selection
and the long name of the selectedfield. That way you don't have to modify all
your target stacks, just the palette scripts.
-- Peter
I think the reply was to trap for suspendStack in your apps, save the current
selection and selectedObject, then trap for resumeStack and set it again. It's
the only way I've found to do it. It's a pain, but not difficult to implement.
I agree that the selection for a stack should not deselect
7.1 I am definitely losing my selection on touching the palette stack
BR
( from my mobile )
On Sat, Oct 24, 2015 at 12:14 AM -0700, "Paul Hibbert"
> wrote:
On Oct 23, 2015, at 19:51, Sannyasin Brahmanathaswami wrote:
>
> I
On Oct 23, 2015, at 19:51, Sannyasin Brahmanathaswami wrote:
>
> I think I asked this before,
>
> but… is there a way to keep the selection when switching to a substack that
> is set to palette?
>
> The goal is to have buttons that operate on selected text, but in a
I think I asked this before,
but… is there a way to keep the selection when switching to a substack that is
set to palette?
The goal is to have buttons that operate on selected text, but in a separate
stack.
Brahmanathaswami
___
use-livecode