On Mon, Apr 6, 2020 at 1:39 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:
> This makes me crazy. I almost never want the first field selected when I
> go to a card,
> particularly on mobile. And god forbid the first field is a list field,
> where the first line is
>
I think about 30% of my coding is one workaround or another. :-)
Bob S
> On Apr 7, 2020, at 3:53 PM, J. Landman Gay via use-livecode
> wrote:
>
> I have workarounds, I just don't want to have to use them. Selecting nothing
> or setting the hilitedline, either one, you still have to set up
I have workarounds, I just don't want to have to use them. Selecting nothing or setting the
hilitedline, either one, you still have to set up some handlers to do it. They don't work in an
openCard handler, you have to reset after that.
On 4/6/20 2:38 PM, Bob Sneidar via use-livecode wrote:
I
I ALWAYS want that. Nevertheless, have you tried select nothing in after
OpenCard?
Bob S
On Apr 6, 2020, at 11:39 AM, J. Landman Gay via use-livecode
mailto:use-livecode@lists.runrev.com>> wrote:
This makes me crazy. I almost never want the first field selected when I go to
a card,
J. Landman Gay wrote:
> I want a property or setting that lets me turn off this default
> behavior. It's annoying and disruptive, and has been there since
> day one.
I lost count of how many times I've seen that come up in the forums over
the years.
What you propose seems reasonable and
On Apr 6, 2020, at 11:39 AM, J. Landman Gay via use-livecode
wrote:
>
> This makes me crazy. I almost never want the first field selected when I go
> to a card, particularly on mobile. And god forbid the first field is a list
> field, where the first line is hilited whenever the stack resumes
This makes me crazy. I almost never want the first field selected when I go to a card,
particularly on mobile. And god forbid the first field is a list field, where the first line is
hilited whenever the stack resumes focus, even if the hilitedline was 0.
The workaround is tedious: on
