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
Don't ignore the autoHilite of a field. Dictionary says:
Specifies whether a button highlights when it's pressed,
or whether selected text in a field is highlighted.
Phil Davis
On 2/24/17 6:18 PM, Bob Sneidar via use-livecode wrote:
Ok I've played with locked, traversalOn, and disabled and t
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 user would expect) and yet prevent the editing of the tex
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
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 play around with it.
Bob S
> On Feb 24, 2017, at 12:35
The difference is, turning traversal off, rather than setting the locktext
to true doesn't work. Even if one manages to hilite text in the
non-traversable field, it isn't really selected. (Which is why if it were
me I'd not do it that way)
On Fri, Feb 24, 2017 at 1:35 PM, Richard Gaskin via use-l
Bob Sneidar wrote:
> On Feb 24, 2017, at 10:06 , Richard Gaskin wrote:
>>
>> That should not be needed.
>>
>> LiveCode allows only one active field selection in non-list fields.
>
> Yes I did. It returns empty. I have a menu which intercepts the
> Copy menu selection. I hilite the text in a field
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 tried the hilitedText
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
> the one which was not empty. I'll play
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 24, 2017, at 0
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 with
that a bit.
Bob S
>
*sigh* my mistake again. Even when selecting a word with script it
doesn't work. (I still had locktext on, combined with traversal being off,
and THAT worked. As soon as I turned the locktext back off it failed to
work)
Shutting up now, till I get some sleep. :D
On Fri, Feb 24, 2017 at 10:36 A
One last thing. On windows, with traversalon and locktext to true, text is
selectable, but as expected there is no insertion point. The only way I
can make a selection with traversalon = false is to double click a word.
This is the opposite of just setting the locktext to true, one can drag and
s
I'll submit one.
Bob S
> On Feb 24, 2017, at 09:21 , Mike Bonner via use-livecode
> 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
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 24, 2017 at 9:50 AM, Bob Sneidar via use-livec
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 way to get the hilited text for a control without
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
24 matches
Mail list logo