LiveCode Forums.

Klaus wrote: Thu Mar 22, 2018 3:24 pm Please take a look at my last comment for that bug!
http://quality.livecode.com/show_bug.cgi?id=20948

The expalantion is really not straightforward, but the observed behavior is definitively correct, once you understand what is going on. Create a ONE line text field with AUTOTAB and see yourself.

Klaus,
I read your comment, ran some tests, and then posted my findings in the LC QC Center.

I'm going to call "bullshit" on this being a "dictionary" issue causing user confusion. This is a real problem I can demonstrate and, regardless of what the dictionary says (or is supposed to say according to Panos), there is inconsistent behavior.

Here's my stack where you can alter the sizes of the fields in the "modal" dialog and see for yourself how inconsistent AutoTab is working.

I had to zip it or the forum wouldn't permit it to be attached.

Barry

rumplestiltskin wrote: Thu Mar 22, 2018 8:42 pm I had to zip it or the forum wouldn't permit it to be attached.

That is actually true for all attachments (that the board accepts, there are a few it doesn't) with the exception of pictures. We actually had a little discussion about it if it is of any interest, it basically boils down to scripts being able to be executable pieces of code, forcing the zip is a precaution.

Thanks for posting that, Barry. Seems to be platform-specific: when I run that here (LC v9rc1 under Ubuntu 14.04) the fields behave as expected. Rather well, actually: when I modified the larger one to make it more than two lines tall, using a Return in the field did add a second line, but using Return again moves to the next field.

Hopefully the team can pin down why this isn't working as well on macOS.

FourthWorld wrote: Thu Mar 22, 2018 9:29 pm Thanks for posting that, Barry. Seems to be platform-specific: when I run that here (LC v9rc1 under Ubuntu 14.04) the fields behave as expected. Rather well, actually: when I modified the larger one to make it more than two lines tall, using a Return in the field did add a second line, but using Return again moves to the next field.

Hopefully the team can pin down why this isn't working as well on macOS.

Thanks, Richard! I guess I'll have to see what happens if I make an application for Mac, Win, and Linux from my stacks in all three platforms. Do the executables from the Mac show the problem but the ones from Linux do not? Or is this known to be only an IDE issue on the Mac?

Hmmm...

Hard to say; I didn't run the test on my Macs.

I'll post this at the bug center.

I can confirm that an app created with the Linux-64 v8.1.9 package results in a Mac app that still exhibits quirky behavior in the fields. A Return-in-field sometimes produces a second line or simply deletes what's already there. I've even seen it simply leaving a "ghost" of the original text "selected" but with the cursor blinking before it; I say "ghost" because that text really isn't there.

Here's the Mac app (generated with the Linux-64 package:
http://cloud2.zoolz.com/s-Hkd5zFRx