Re: Bug, feature, or just something I need to program around?

2021-05-12 Thread J. Landman Gay via use-livecode
Try setting the autoTab property of the field to true. When I do that, tabbing into the field selects all the text, but clicking does not. And shift-arrow does select text after that. LC seems to be a little backward from what you expect. On 5/12/21 3:02 PM, Alex Tweedly via use-livecode wrote:

Re: Bug, feature, or just something I need to program around?

2021-05-12 Thread Alex Tweedly via use-livecode
I don't follow you Jim. Each Note in the Notes app is a multi-line field, and they all behave just the same as multi-line fields in LC (i.e what I think of as "properly" - TABbing into the field positions the cursor with nothing selected, and an immediate cmd-shift-arrow will select all charac

Re: "select the selectedchunk"

2021-05-12 Thread Mark Smith via use-livecode
Remarkable. It completely changes the “selection” behavior of the cursor when cmd-shift-arrow is typed. > On May 12, 2021, at 3:26 PM, Alex Tweedly via use-livecode > wrote: > > select the selectedchunk ___ use-livecode mailing list use-livecode@li

Re: Bug, feature, or just something I need to program around?

2021-05-12 Thread Jim Lambert via use-livecode
> In a LC single line field (MacOS), the keys shift-cmd-rightarrow will > select from the current position to the end of the line, and add that to > the selection. > > BUT if I TAB into the field the cursor is initially at the start of the > field and the key sequence above will move the curs

Re: Bug, feature, or just something I need to program around?

2021-05-12 Thread Alex Tweedly via use-livecode
Thanks Sean - but the text cursor shouldn't always be at char 0. It is the first time you visit the field, but if you  - visit the field  - move the cursor within it  - go off somewhere else  - and later TAB back into that field, the text cursor should be restored to wherever you left it. That is

Re: Problems with text data fields pulling from SQL

2021-05-12 Thread Paul Dupuis via use-livecode
Possibly an encoding issue? If the text in the database was in Unicode or some non-ASCII encoding, then it may appear as one or more question marks in LC unless textEncode/textDecode (I forget which would apply) is used to translate it from the database encoding On 5/12/2021 9:38 AM, Skip Kim

Problems with text data fields pulling from SQL

2021-05-12 Thread Skip Kimpel via use-livecode
I am pulling data from an Azure MS SQL database using an ODBC connection. All data comes across just fine EXCEPT for data with field types of NVARCHAR(Max). When those fields arrive to LC, it shows up as a question mark "?". Any reason why this would happen? Any resolution to this? Best regard

Re: Bug, feature, or just something I need to program around?

2021-05-12 Thread Alex Tweedly via use-livecode
Thanks Mark. Yes, it is in a sense a workaround - but it's a workaround the user see/does. I was hoping to avoid the "surprise" when this one common case doesn't do what she/he would expect. Oh - and I've just found the workaround on openfield    select the selectedchunk end openfield I'll

Re: Bug, feature, or just something I need to program around?

2021-05-12 Thread Sean Cole (Pi) via use-livecode
on openField select char 0 of me end openField On Wed, 12 May 2021 at 09:03, Mark Smith via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi Alex, what sequence are you trying to do that won’t work? If you tab > into a field and then cmd-arrow (right or left) I think it restores the >

Re: Bug, feature, or just something I need to program around?

2021-05-12 Thread Mark Smith via use-livecode
Hi Alex, what sequence are you trying to do that won’t work? If you tab into a field and then cmd-arrow (right or left) I think it restores the “selection” behavior you are looking for ie. you can then shift-cmd-right or left to select the chars. Would that be a work-around? > On May 11, 2021,