Page 1 of 1
When project loads, cursor is in "selection mode"
Posted: Wed Mar 10, 2021 5:52 pm
by xyz
I have a slightly annoying issue. When I first load my project the trackpad cursor is in "selection mode", so when I move the cursor a "dashed rectangle" outline is shown and the pointer starts selecting items on the card. This is no big deal. I just click on the card and the selection mode stops, but it is a little annoying.
This only happens on one of my projects, none of the others. I tried setting the focus to one of my controls (a list field) when I open the card to see if that would eliminate the problem but it has not. I assume that there is some setting that I have inadvertently set that is causing this. I would like to turn it off.
Thanks
Re: When project loads, cursor is in "selection mode"
Posted: Wed Mar 10, 2021 5:56 pm
by richmond62
Probably something in an openStack / openCard script?
Re: When project loads, cursor is in "selection mode"
Posted: Wed Mar 10, 2021 6:19 pm
by Klaus
Hm, I just tested this and found that the TOOL is/stays the one that was selected right before opening an existing project.
So I would consider this "normal" behavior.
Re: When project loads, cursor is in "selection mode"
Posted: Wed Mar 10, 2021 6:21 pm
by kdjanz
Try saving the stack while in run mode, then closing the stack. When you reopen the stack next time, is it in edit mode or run mode?
Re: When project loads, cursor is in "selection mode"
Posted: Wed Mar 10, 2021 6:30 pm
by dunbarx
Richmond nailed this. Put an "openCard" handler in the card script:
Code: Select all
on openCard
choose browse tool
end openCard
Craig
Re: When project loads, cursor is in "selection mode"
Posted: Wed Mar 10, 2021 8:39 pm
by xyz
Thank you all.
To answer kdjanz, "yes, saving after putting the project in run/browse mode and then closing the stack" seems to have solved the problem. Now, regardless of whether I am in "browse" or "pointer" mode when I save and close, the pointer/cursor is no longer set to "select objects" when I open the project. But, I am curious why the problem persisted as long as it did since I had gone through several "save cycles." At any rate, the problem seems to be fixed.
Thank you all.