You have probably already looked at these but here are (some of) the scroller
settings I use for the below-mentioned field:
mobileControlSet sScrollerId, "pagingEnabled", "false"
mobileControlSet sScrollerId, "decelerationRate", "normal" -- fast --iOS only
mobileControlSet
I'm doing something very similar but the problem is that I don't get any
mouse or touch messages at all, which is why I'm thinking it must be the
settings for my ios scroller.
Whatever the defaults are for delayTouches and canCancelTouches, I think at
least one of them needs to be changed.
Graham Samuel wrote:
> Well, I am happy to be wrong, so I repeated exactly what you did, of
> course using my own bit of styled text. It didn’t work - partly
> because I can only select the text in the field itself in ‘run’ mode,
> but I can only see the Inspector in ‘edit’ mode. When I switch
Just saw an improvement in my code that *should* make it happy to work with
Unicode characters…
local OkayChars = ""
function CleanASCII3 DerText if OkayChars = "" then -- construct OkayChars
string as needed repeat with K1 = 32 to 126 put numToChar (K1) after
OkayChars end repeat
While Bob Sneidar's function should do the job of scrubbing weird characters
from text, am unsure why he felt the need to construct that massive pCustomList
variable. Seems to me that it would be simpler, and perhaps quicker, to do this
instead:
function cleanASCII2 DerASCII put "" into
You're almost there Paul!
On 5/19/20 2:18 PM, Paul Dupuis via use-livecode wrote:
I have a set of custom properties in stack "X", a lot of which begin
with "options_"
So I assume these are members of a customPropertySet, whose name I'll
call "myOptions".
I want to loop through them and
Of course I forgot to declare the local and global variables...
global gHorizontalSwipeDistance
global gVerticalSwipeDistance
local lMouseStartV
local lMouseStartH
> On May 19, 2020, at 3:20 PM, scott--- via use-livecode
> wrote:
>
> I’m using this script on iOS directly inside a LC field
I’m using this script on iOS directly inside a LC field object in order to get
a "delete button” to appear. (Ya, I know that is pretty ancient UI) But it
requires a swipe on iOS which is what you are after. I don’t think it is
responsive enough to do some of the fancy pushes that differentiate
I don't have an answer and hope someone else does. I hate my workaround.
My workaround is to leave a space on either side of the field (45 px or so..
haven't tried to minimize).
After the user gets frustrated enough, they end to do a swipe near the edge of
the screen (across the blank space and
Would the problem be due to the settings for canCancelTouches and delayTouches? What are the
defaults? And what behaviors do they control exactly? I can't quite figure out what the
dictionary is saying.
On 5/19/20 4:21 PM, J. Landman Gay via use-livecode wrote:
I have a tall field inside a
Graham,
If you click the lock icon on the property inspector while you’re in edit mode,
the PI for that object will remain open when you switch back to run mode.
Hope this helps.
Devin
> On May 19, 2020, at 3:10 PM, Graham Samuel via use-livecode
> wrote:
>
> Well, I am happy to be wrong,
I have a tall field inside a shorter group that uses a mobile scroller. A behavior assigned to
the group handles the scrolling and checks for swipes by capturing mouseDown and mouseUp to
determine touch locations so it can calculate the direction of the swipe. This works on Android.
On iOS I
I have a set of custom properties in stack "X", a lot of which begin
with "options_"
I want to loop through them and get the values, so I have:
local tDisplayList
put the customKeys of stack "X" into tProperties
filter lines of tProperties with "options_*"
if tProperties is empty then
Well, I am happy to be wrong, so I repeated exactly what you did, of course
using my own bit of styled text. It didn’t work - partly because I can only
select the text in the field itself in ‘run’ mode, but I can only see the
Inspector in ‘edit’ mode. When I switch between the two modes, I
I was trying the same thing in LC 9.6 (dp4) and it works here. It works both
when selecting the text in the text pane in the navigator or selecting text in
the field itself.
Regards
Tore Nilsen
> 19. mai 2020 kl. 19:53 skrev Richard Gaskin via use-livecode
> :
>
> I just tried this recipe:
>
Graham Samuel wrote:
> To an ordinary LC developer, if you can change the properties of the
> initial text (to a different size for example) without overtly
> selecting it, then the same behaviour can be expected from the IDE
> when trying to change text you’ve pasted in. It may or may not be
>
Well, Tore, I think this is a rather purist view! To an ordinary LC developer,
if you can change the properties of the initial text (to a different size for
example) without overtly selecting it, then the same behaviour can be expected
from the IDE when trying to change text you’ve pasted in.
I had to write a function that returns only true ASCII printable characters
because when I performed a drag/drop operation from a searchable PDF, I
discovered that Acrobat puts all kinds of hidden characters in the text that
really messes with LC. It’s a simple function:
FUNCTION cleanASCII
I am not sure this is a bug. When you use the normal paste function you
actually paste in styled text. New text, following the text you pasted in will
inherit the styling of the last character of the text you pasted into the
field. This then would work the same way as if you selected some text
Yep, that was it! I had pasted some text from elsewhere. The text **looks**
perfectly normal (and the count of characters is the same as in the visual
representation of them, so none apparently hidden), but in some way it must
mess up the functioning of the Property Inspector. As Ralph
20 matches
Mail list logo
