Richard that script snippet actually helped me solve a different problem. I
remember now why I was using traversalOn instead of lockText. I have certain
fields I do not want users to edit, so I set the lockText to true. I then have
a handler called enableForm that enables every field and button
Oh right you are! The thing that was throwing me is double-clicking does not
work, but I can triple click and it selects the whole chalupa and I can copy
it. I can also drag select. This will work.
Bob S
> On Feb 28, 2017, at 10:52 , J. Landman Gay via use-livecode
> wrote:
>
> On 2/28/17
On 2/28/17 9:58 AM, Bob Sneidar via use-livecode wrote:
I just think that LC should work like virtually every other forms
based app I've ever used, where being editable is not a prerequisite
for copying text.
Did you try the field settings I suggested? It does work, it's already
built-in:
au
Bob Sneidar wrote:
> On Feb 24, 2017, at 22:09 , Richard Gaskin wrote:
>>
>> on rawkeydown k
>> if k = 99 then
>> if the commandKey is "down" then copy
>> end if
>> end rawkeydown
>
> For that matter I could just check the status of the "state" property
> (view | new | edit) to allow/dis
For that matter I could just check the status of the "state" property (view |
new | edit) to allow/disallow editing. Not saying there are not workarounds. I
just think that LC should work like virtually every other forms based app I've
ever used, where being editable is not a prerequisite for co
For a scriptless solution that's purely property-driven, what Jacque
said covers normal click-and-drag selection at the small cost of
multi-click selection.
And if you need multi-click selection and don't mind a small bit of
scripting, putting this in a normal editable field seems to make it
On 2/24/17 8:18 PM, Bob Sneidar via use-livecode wrote:
Ok I've played with locked, traversalOn, and disabled and the only
thing that alows me to enable/disable editing of the contents of a
field is traversalOn. No combination of the other settings allow me
to select text (in any manner that a us
Think of a web form. You can copy text all the
live long day and yet not be allowed to edit it. That is what I am shooting for.
I agree that if copying is not allowed, or to put it another way, if getting
the selectedText or hilitedText is not possible, then the UI should not
indicate that text
er to select and copy
data from an uneditable field. Think of a web form. You can copy text all the
live long day and yet not be allowed to edit it. That is what I am shooting
for.
I agree that if copying is not allowed, or to put it another way, if getting
the selectedText or hilitedText i
Bob Sneidar wrote:
Hi Richard. You are "locking" fields. I am setting the traversalOn
to false. The reason I use this is because a locked field will still
show the focus border, which I do not want.
The focus border should be governed independently, using the
showFocusBorder property.
If you
On 2/24/17 3:33 PM, Bob Sneidar via use-livecode wrote:
Hi Richard. You are "locking" fields. I am setting the traversalOn to
false. The reason I use this is because a locked field will still
show the focus border, which I do not want. I suppose I can lock the
field and lock the field. I will pla
, 2017, at 12:35 , Richard Gaskin via use-livecode
> wrote:
>
> If has one menu and a simple script in it:
>
> on menuPick pItemName
> put the selectedText
> end menuPick
>
> So here everything I do with selections in locked fields gives me the same
> results
t fields.
> >
> > Yes I did. It returns empty. I have a menu which intercepts the
> > Copy menu selection. I hilite the text in a field whose traversalOn
> > is false, then select Copy from the menu. In the menu handler I have
> > "put the selectedText". I also
ection. I hilite the text in a field whose traversalOn
> is false, then select Copy from the menu. In the menu handler I have
> "put the selectedText". I also tried "hilitedText". Neither work. I
> also tried the hilitedText of field "fldIPAddress". No
Yes I did. It returns empty. I have a menu which intercepts the Copy menu
selection. I hilite the text in a field whose traversalOn is false, then select
Copy from the menu. In the menu handler I have "put the selectedText". I also
tried "hilitedText". Neither work. I also t
Bob Sneidar wrote:
> Enhancement Request 19323 submitted.
>
> As to your post, yes the selectedText 'of the field' will work.
> But a menu command like "Copy" would not know which field was
> selected. I suppose I could loop through all the fields and get
>
If by "as expected" you mean the selectedText of the field can be obtained,
then this is likely because you set it with the button. Selecting it with a
cursor does not behave the same way. How odd. I may have to dig into the IDE
and find where this is happening.
Bob S
> On Feb
Enhancement Request 19323 submitted.
As to your post, yes the selectedText 'of the field' will work. But a menu
command like "Copy" would not know which field was selected. I suppose I could
loop through all the fields and get the one which was not empty. I'll play
of just setting the locktext to true, one can drag
> and select, but multi clicks don't select. getting the selectedtext of
> field "whatever" does indeed work. (and you could turn off the focusborder
> too)
>
> My guess is that despite the hilite that appears when travers
select, but multi clicks don't select. getting the selectedtext of field
"whatever" does indeed work. (and you could turn off the focusborder too)
My guess is that despite the hilite that appears when traversal is off, the
text isn't actually selected. To test this, I
uot;fieldname" is an optional argument youcan use.
>>
>> get the selectedtext of field "myfield"
>>
>> On Fri, Feb 24, 2017 at 9:50 AM, Bob Sneidar via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>
>>>
Nevermind, it doesn't work, and I think it should. Enhancement request?
Bug?
On Fri, Feb 24, 2017 at 10:16 AM, Mike Bonner wrote:
> of field "fieldname" is an optional argument youcan use.
>
> get the selectedtext of field "myfield"
>
> On Fri, Feb
of field "fieldname" is an optional argument youcan use.
get the selectedtext of field "myfield"
On Fri, Feb 24, 2017 at 9:50 AM, Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Hi all.
>
> The Short Version:
>
> Is there a
Hi all.
The Short Version:
Is there a way to get the hilited text for a control without focus?
The Long Version:
I use a method for forms (by which I mean LC cards with fields and buttons on
them) where I set the traversalOn to false on all the fields when I am simply
viewing the data, so t
"Bengalis always cause
problems."
Richmond.
On 13.11.2016 12:21, Richmond wrote:
Does anyone have any idea why when in Livecode 6.x if one
has this:
on mouseUp
set the useUnicode to true
set the unicodeText of the selectedText to numToChar(4000)
end mouseUp
it inserts the charact
Does anyone have any idea why when in Livecode 6.x if one
has this:
on mouseUp
set the useUnicode to true
set the unicodeText of the selectedText to numToChar(4000)
end mouseUp
it inserts the character between the chars where the insertion point is
inwith a field,
but in Livecode
> On Nov 6, 2016, at 9:41 AM, Richmond <mailto:richmondmathew...@gmail.com>> wrote:
>
> I wonder why this:
>
> set text of the selectedText to numToCodePoint(2309)
>
> [when I have a textField with a selection point within it]
>
> doesn't work (LC 8.
I wonder why this:
set text of the selectedText to numToCodePoint(2309)
[when I have a textField with a selection point within it]
doesn't work (LC 8.1).
Richmond.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this u
useUnicode to true
>>> set the unicodeText of the selectedText to numToChar(2340)
>>>select after char -1 of field X
>>> end mouseUp
>> Untested, but what about
>>
>> on mouseUp
>> local tChunkChar, tChunkField
>>
>> set the useUnicod
On 07/06/2011 10:38 AM, Mark Wieder wrote:
Richmond-
Wednesday, July 6, 2011, 12:19:41 AM, you wrote:
I have just tried this:
on mouseUp
set the useUnicode to true
set the unicodeText of the selectedText to numToChar(2340)
select after char -1 of field X
end mouseUp
Untested
Richmond-
Wednesday, July 6, 2011, 12:19:41 AM, you wrote:
> I have just tried this:
> on mouseUp
> set the useUnicode to true
> set the unicodeText of the selectedText to numToChar(2340)
>select after char -1 of field X
> end mouseUp
Untested, but what about
On 07/06/2011 10:10 AM, Slava Paperno wrote:
The selectedText doesn't work with Unicode.
I have a very similar thing working fine: I use "select after char -1 of
field X".
Slava
set the unicodeText of the selectedText to numToChar(2340)
works 100%
and THAT is not my probl
The selectedText doesn't work with Unicode.
I have a very similar thing working fine: I use "select after char -1 of
field X".
Slava
> -Original Message-
> From: use-livecode-boun...@lists.runrev.com [mailto:use-livecode-
> boun...@lists.runrev.com] On Beha
a.k.a. "Richmond's longest-lasting headache"
imagine this sort of script:
on mouseUp
set the useUnicode to true
set the unicodeText of the selectedText to numToChar(2340)
select after the selectedText
end mouseUp
all looks straightforward (nicht?), but
Yes! "the unicodetext of the selection" is the answer. Forget the
selectedText.
"the unicodetext of the selectedChunk" works as well.
Thank you, Mark!
S.
> -Original Message-
> From: use-livecode-boun...@lists.runrev.com [mailto:use-livecode-
> boun...@l
Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50277553
New: Download the Installer Maker Plugin 1.6 for LiveCode here http://qery.us/ce
On 17 jun 2011, at 09:31, Slava Paperno wrote:
> Briefly, here is the problem:
>
> put the selectedTex
Briefly, here is the problem:
put the selectedText of field "BilingualText" of this card into
tCurrSelection
--the field may hold, for example, the two words Боб Bob, which is the
string assigned to the unicodeText prop. of the field
set the unicodeText of field "YourSelection&q
On 05/01/2011 06:35 AM, J. Landman Gay wrote:
On 4/30/11 9:57 PM, dunb...@aol.com wrote:
Repost of my riposte.
Richmond.
Would changing to "select after the text" make this better?
That's what I'd do too. "select after the text of fld 1", or just
"select after fld 1".
Thank you.
Yes,
On 05/01/2011 05:57 AM, dunb...@aol.com wrote:
Repost of my riposte.
Richmond.
Would changing to "select after the text" make this better?
Craig
The script editor tells me that's wrong, as it would had you tried it .
. . :)
___
use-livecode
On 4/30/11 9:57 PM, dunb...@aol.com wrote:
Repost of my riposte.
Richmond.
Would changing to "select after the text" make this better?
That's what I'd do too. "select after the text of fld 1", or just
"select after fld 1".
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
Repost of my riposte.
Richmond.
Would changing to "select after the text" make this better?
Craig
-Original Message-
From: Richmond Mathewson
To: How to use LiveCode
Sent: Sat, Apr 30, 2011 4:26 pm
Subject: Repost of "selectedText"
Sorry chaps; just a
filled up with unicode (double-byte)
chars, and to make sure the
next chars gets placed in the correct place my insertion routine ends with
select after the selectedText
HOWEVER, when my line of text gets near to the edge of my textField I
tend to hit the RETURN
or ENTER button on my keyboard
t; From: Richmond
> To: How to use LiveCode
> Sent: Fri, Apr 29, 2011 4:51 am
> Subject: select after the selectedText
>
>
> So, here I am with a large textField, and as I merrily type into it new
> characters keep getting
> added to the end of the string (as one would exp
Richmond.
Would changing to "select after the text" make this better?
Craig
-Original Message-
From: Richmond
To: How to use LiveCode
Sent: Fri, Apr 29, 2011 4:51 am
Subject: select after the selectedText
So, here I am with a large textField, and as I merrily type i
insertion routine ends with
select after the selectedText
HOWEVER, when my line of text gets near to the edge of my textField I
tend to hit the RETURN
or ENTER button on my keyboard and start a new line . . .
after which things go "funny", and the select after the selectedText
kee
45 matches
Mail list logo
