I have an app where after some preliminary actions, an ‘editable window’ (i.e.
a normal window) is shown with a palette. When the app reaches this stage, for
some reason the main (top) stack - i’ve checked that it really is the topStack
- doesn’t have the focus and its menus don’t work. I have t
On Dec 6, 2014, at 7:44 AM, Graham Samuel wrote:
> I have an app where after some preliminary actions, an ‘editable window’
> (i.e. a normal window) is shown with a palette. When the app reaches this
> stage, for some reason the main (top) stack - i’ve checked that it really is
> the topStack -
If the palette is the last stack to open, it may be the defaultstack even
though it isn't the topstack. So after the opening sequence completes, try
adding a command to set the defaultstack to the mainstack.
On December 6, 2014 6:44:15 AM CST, Graham Samuel wrote:
>I have an app where after so
Thanks to Peter and Jacque for these suggestions. Sadly, neither of them
worked. Neither did ‘click at the loc of this cd’ or similar statements. The
only thing that works so far is a real mouse click in the body of the mainstack
window or on its title bar. After that is done and focus has once
I have seen such issues having invisible stacks, that is when I was
hiding some stacks not closing them during the open sequence. Somehow
they got focus at the end and did not release it happily. This was in
earlier versions, though.
RObert
On 06.12.2014 at 23:00 Uhr + Graham Samuel appar
One last thing to try:
toplevel "main"
set the defaultstack to "main"
Also, if you haven't already, assign the menu to the palette stack too. You may
need to change the menu scripts to check whether the target stack is the
palette or not, if some of the commands don't apply to the palette.
