autotab gives me a headacke

[Thierry]

Hi all,

What could prevent the autotab set to true to work ?

I can navigate between my fields with the TAB but pressing the return, this adds a newline in any of the fields

I'm on Mac , LC 8.1.3 and this happens in the IDE or on my iPad.


Thanks for any hint,

Thierry

[Lagi Pittas]

Hi Thierry,

I have no answer to this but it has cropped up good a few times with me and I keep thinking I've misunderstood /mis-remembered the dictionary or the way it is supposed to work.
I just tested on version 6.7.11 and yes just clicking on <tab on return> works how i originally understood it - replace the return with a tab that goes to the next field - exactly as God intended it to work.

I have an app where i had to put a type TAB in the on ReturnInfield even because of the same problem you have - so it seems it hasn't been fixed up to version 8.
I "fixed" it by copying the controls and code across to the a new stack fixes it - I'm not teaching my granny to suck eggs, you already know that - but it would be good to know why it happens

Sorry I can't be of any help other than to thank you for confirming to me that I wasn't going mad "mis remembering" how it is supposed to work.

Lagi

[Thierry]

Sorry I can't be of any help other than to thank you for confirming to me
that I wasn't going mad "mis remembering" how it is supposed to work.

Thanks Lagi,

At least, I'm not the only one!
This hopefully will wake up some Angel-coders in Edinburgh to kill our madness

Unfortunately, I'm preparing a demonstration for one my latest work and it needs to be LC8 or more.

I will rewrite my stack from scratch and see what happen...

Regards,

Thierry

[FourthWorld]

It works here in 8.1.4; I don't have v8.1.3 installed to test. If you still see this in the newer version, double-check that the field height is no greater than the textHeight+margins+borderWidth.

[Thierry]

It works here in 8.1.4; I don't have v8.1.3 installed to test. If you still see this in the newer version, double-check that the field height is no greater than the textHeight+margins+borderWidth.

Thanks Richard,

I'm still with LC 8.1.3 at the moment.

Here is a simple Test stack with some explanations.
I added a "check fields" button which shows the fields settings.


BTW, the TAB key is broken too here

Test2.livecode.zip

(1.97 KiB) Downloaded 259 times

Thierry

[Lagi Pittas]

Curiouser and Curiouser said Alice ....

I ran the stack on version 8.1.2 and as you say it doesnt get to the Field with ccccc in it.

But ... if you go to the message box and type put field 3 it prints "bbbb" , put field 2 prints "aaaa" (both correct)

It also failed to work if I copied the field that was outside the group inside the group - the return and tab stopped working.

So copying them outside the group they worked.

By a bit of deduction I found out that you have to untick "the contents focus with keyboard" if the fields are inside the group.

Now to me it would be the "focus with keyboard" that should be unticked - Maybe mark can come in here and tell us the nuances of those two options.

But Now I know

Regards Lagi

[Thierry]

Curiouser and Curiouser said Alice ....

By a bit of deduction I found out that you have to untick "the contents focus with keyboard" if the fields are inside the group.
Now to me it would be the "focus with keyboard" that should be unticked - Maybe mark can come in here and tell us the nuances of those two options.
But Now I know

thanks for checking Lagi,

Ok, but I would like to keep my fields inside a group.
This is the simplest stack I could make to see the strange behavior
but my official stack is a bit moooore complicate.

Funny with "the contents focus with keyboard" and "focus with keyboard" as I did checked the 4 combinations...
Hmmm, may be I don't have a headacke but a tabReturnKeyField virus ?

So, I'll try again with your group settings.

Thanks again and I will send you a funny regex as a gift

Thierry

[Thierry]

Mmmm,

Following Lagi's idea, here is a screenshot of my stack with
the group inspector. I did play nicely with the tab and return but look the middle field:
I have an extra return in it ? where does it come from?

Any hints ?

Thierry

[FourthWorld]

The issue only affects the second field in the tab group. Any other fields outside the group work as expected. This prompted me to look at the group's properties, and I found that the group's tabGroupBehavior is set to true. Turning that off appears to correct the problem.

FWIW I find the subset of properties handled by LC's Inspector useful, but sometimes I need a more complete list. So I made a property sheet for that, 4W Props, available in the Stack Files section of LiveNet - in the IDE see Development -> Plugins -> GoLiveNet

[Thierry]

I found that the group's tabGroupBehavior is set to true. Turning that off appears to correct the problem.

Well, thanks Richard for finding out the problem.

Mmm, without doing something deliberately, I have now my tabGroupBehavior set to false
and as you said, it works fine.

So, next question is what makes this setting changes from the LC's inspector as I didn't set it?

Regards,

Thierry

[FourthWorld]

So, next question is what makes this setting changes from the LC's inspector as I didn't set it?

That's a very good question. I just checked v7.0 and v8.1.4 and in both the tabGroupBehavior is set to false for newly created groups. Maybe a bug specific to some version between those two?

[Thierry]

So, next question is what makes this setting changes from the LC's inspector as I didn't set it?

That's a very good question. I just checked v7.0 and v8.1.4 and in both the tabGroupBehavior is set to false for newly created groups. Maybe a bug specific to some version between those two?

Well, started this test stack from scratch with LC 8.1.3.
Coming back with a fresh mind after a morning walk in the forest,
I decided to stress a bit this demo stack and:

1st everything works , I can TAB or RETURN from any of the fields with some text in it and all is fine.

next, I edit the last field outside the group and empty the textSize property from the inspector palette
and/or changing the height of the field

next, BOOM ! BANG ! BADABOOM

playing with some RETURN, I loose the text of the other fields plus the selection half on top of the field.


Re-defning a textSize + selecting "fit to contents" for the height of the field seems to make things clean again.

Well, that's all I can say and I have no more time to spend on this...

And thanks again Lagi and Richard for your help.

Thierry