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 Peter M. Brigham pmb...@gmail.com http://home.comcast.net/~pmbrig On Oct 26, 2015, at 11:16 AM, Bob Sneidar wrote: > 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 when > switching to another stack or app. I suppose then that the selection should > be a stack property instead of a global one, but I don't see how they could > change it now. > > Bob S > > >> On Oct 23, 2015, at 19:51 , Sannyasin Brahmanathaswami <bra...@hindu.org> >> 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 separate >> stack. >> >> Brahmanathaswami >> >> _______________________________________________ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
