Re: workaround for cut-off text in native scroller?

2021-06-04 Thread Curry Kenworthy via use-livecode 

Jacque wrote:
> It's either the Flying Spaghetti Monster or fullscreenmode. ;)

For Dawkins so loved the things of this world
Might be good to steer away from such, and back to LC. :)

Richard:

> I'm still wondering why we're still scripting scroll regions at all.
...
> I'm also wondering why I'm alone in wondering that...

Why think you're alone, Brother Richard? Many are wondering.

Besides some buggy implementations, many of LC's mobile features seem to 
ignore LC's own stated paradigm: cross-platform, "live" code.


That's why I've often opted to use standard features instead.
Write once, truly runs everywhere, including IDE. Very consistent.

But of course tying the two together would be better still.
Write once, run everywhere, with native quality and nuance.
And the ability to easily switch back to standard features.

(Thanks for preaching on this. I've been sick the whole week.
So still in feverish lurk mode. But no, you're not alone! Take care.)

Best wishes,

Curry Kenworthy

Custom Software Development
"Better Methods, Better Results"
LiveCode Training and Consulting
http://livecodeconsulting.com/

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-03 Thread Jim Lambert via use-livecode 
> Jacque wrote:
> It's either the Flying Spaghetti Monster or fullscreenmode. ;)


Flying Spaghetti Monster is what I call my code.

Jim Lambert

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

RE: workaround for cut-off text in native scroller?

2021-06-02 Thread Ralph DiMola via use-livecode 
native scroller?
I add 20 to the bottom of the "contentrect". This has worked fine for me in 
various apps. Your mileage may vary.

On resizing... JLM answered me on my "LiveCode day 1(4.x)" use list request and 
informed me that I have to roll my own so I spent the next 2-3 months making a 
general use resizing library that has worked well for me though the years. I 
have never used the newer built in options. The nice thing is that my library 
is handy for the very few desktop apps I have made.

Notes on below:
1. NEVER lock message just to handle resizing.
True true. This can get you into real trouble.

2. ALWAYS (and I mean always) set the lockLoc of a group.
True again with a caveat. If your creating a group by script you have to add 
one control in the group before you set the group's lockloc then rect of the 
group. Then you can start placing other controls in the group and it will not 
change size/position.

3a. Always resize/reposition things by setting their rect (not their 
top/left/width/...).
The rules I have gleaned is.
 a) Yes, the rect is always absolute.
 b) For best performance set the control's rect ONCE.
 c) Set the height/width before top/left/bottom/right if using the 
top/left/width/height. This is slow because the engine has to rerender after 
every size/pos change.
 d) When changing the width/height with ONLY even or ONLY odd numbers the 
control will remain centered. But if you use odd and even numbers the it will 
walk to the left/top. If you for example set the width to 100 then 101 then 100 
then 101. The control will walk left by 1 pixel for every 100/101 width setting 
change. I can see why LC is attempting to keep the control centered I guess but 
keeping the top/left constant whilst changing the height/width would produce 
more predictable results.


Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of 
Alex Tweedly via use-livecode
Sent: Wednesday, June 02, 2021 7:43 AM
To: use-livecode@lists.runrev.com
Cc: Alex Tweedly
Subject: Re: workaround for cut-off text in native scroller?


On 02/06/2021 04:18, Mark Wieder via use-livecode wrote:
>
> I do ok on resizing routines until it comes to groups. Then I always 
> end up reinventing things: when and where to lock messages, how to get 
> things resized in the right order so as not to undo what I just did...
>
> If there are any rules of thumb I'd love to know them.
>
I can tell you mine - they work for me , but whether they work for you, or 
anyone else, is a different matter.

1. NEVER lock message just to handle resizing.
   If you need to do that, you're already in a heap of trouble :-)

2. ALWAYS (and I mean always) set the lockLoc of a group.
 Don't let those uppity groups change their size - you need to be in charge 
:-)

3. Work top-down in a (fairly) strict hierarchy. Let each level of card/group 
handle the layout of its component pieces, allocate space for them and "set the 
rect .." for each.

3a. Always resize/reposition things by setting their rect (not their 
top/left/width/...).
   Every time I try to use those seemingly-convenient shorter forms, I get 
in trouble :-)

4. Design in some logging mechanism so that if something is going wrong, you 
can easily turn on logging and see what is happening, across ALL your resizing 
group / controls.

5. In the very rare occasions where there is need to cross the hierarchy as 
above, do it explicitly (e.g. I have a convention of sometimes having a handler 
"presizecontrol" which returns a *preferred* size or minimum size, which the 
upper levels of the hierarchy can use to check what lower layer groups would 
like to be, can adjust their decisions accordingly - and then resize ("set the 
rect ..") accordingly.

Alex.



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-02 Thread Mark Wieder via use-livecode 

On 6/2/21 4:42 AM, Alex Tweedly via use-livecode wrote:

I can tell you mine - they work for me , but whether they work for you, 
or anyone else, is a different matter.


Thanks for the pointers.



1. NEVER lock message just to handle resizing.
   If you need to do that, you're already in a heap of trouble :-)


Been there. Got the t-shirt.



2. ALWAYS (and I mean always) set the lockLoc of a group.
     Don't let those uppity groups change their size - you need to be in 
charge :-)


Ok - that's one I should take more to heart.



3. Work top-down in a (fairly) strict hierarchy. Let each level of 
card/group handle the layout of its component pieces, allocate space for 
them and "set the rect .." for each.


3a. Always resize/reposition things by setting their rect (not their 
top/left/width/...).
   Every time I try to use those seemingly-convenient shorter forms, 
I get in trouble :-)


Yes, but... there are some cases where I need to set the height/width 
explicitly. For instance, I've got a complex group that contains a 
circle inside a rectangle. I could, I suppose, calculate the new height 
of the circle but not set it, then calculate the rectangle and center 
point of the circle and set the rectangle coordinates from that


Instead, I just set the height and width of the circle within the group, 
and this mostly seems to work if I'm careful.


--
 Mark Wieder
 ahsoftw...@gmail.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-02 Thread Alex Tweedly via use-livecode 


On 02/06/2021 04:18, Mark Wieder via use-livecode wrote:


I do ok on resizing routines until it comes to groups. Then I always 
end up reinventing things: when and where to lock messages, how to get 
things resized in the right order so as not to undo what I just did...


If there are any rules of thumb I'd love to know them.

I can tell you mine - they work for me , but whether they work for you, 
or anyone else, is a different matter.


1. NEVER lock message just to handle resizing.
  If you need to do that, you're already in a heap of trouble :-)

2. ALWAYS (and I mean always) set the lockLoc of a group.
    Don't let those uppity groups change their size - you need to be in 
charge :-)


3. Work top-down in a (fairly) strict hierarchy. Let each level of 
card/group handle the layout of its component pieces, allocate space for 
them and "set the rect .." for each.


3a. Always resize/reposition things by setting their rect (not their 
top/left/width/...).
  Every time I try to use those seemingly-convenient shorter forms, 
I get in trouble :-)


4. Design in some logging mechanism so that if something is going wrong, 
you can easily turn on logging and see what is happening, across ALL 
your resizing group / controls.


5. In the very rare occasions where there is need to cross the hierarchy 
as above, do it explicitly (e.g. I have a convention of sometimes having 
a handler "presizecontrol" which returns a *preferred* size or minimum 
size, which the upper levels of the hierarchy can use to check what 
lower layer groups would like to be, can adjust their decisions 
accordingly - and then resize ("set the rect ..") accordingly.


Alex.



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread Mark Wieder via use-livecode 

On 6/1/21 3:53 PM, Richard Gaskin via use-livecode wrote:

If I ever get around to writing an article on resizing strategies I'll 
keep that in mind.  Helpful to learn about one more xTalk veteran in the 
same boat.




I do ok on resizing routines until it comes to groups. Then I always end 
up reinventing things: when and where to lock messages, how to get 
things resized in the right order so as not to undo what I just did...


If there are any rules of thumb I'd love to know them.

--
 Mark Wieder
 ahsoftw...@gmail.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread J. Landman Gay via use-livecode 
On June 1, 2021 9:13:24 PM Richard Gaskin via use-livecode 
 wrote:



Seems I'd misunderstood the two bug reports and Brian Milby's suggestion
in this thread.  This scroll calculation issue is not specific to the
changed metrics from fullScreenMode?


Maybe. I understood Brian's post to mean that was his theory but it needed 
testing. I suppose it would make sense.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com





___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread Richard Gaskin via use-livecode 

J. Landman Gay wrote:

> Richard wrote:
>> Alternatively, you could handle your layout
>> the way most apps on your phone do, with
>> responsive design.
>
> That would manage the overall layout but wouldn't fix the error in
> the native scroller.

Seems I'd misunderstood the two bug reports and Brian Milby's suggestion 
in this thread.  This scroll calculation issue is not specific to the 
changed metrics from fullScreenMode?


--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread J. Landman Gay via use-livecode 

Alternatively, you could handle your layout
the way most apps on your phone do, with
responsive design.


That would manage the overall layout but wouldn't fix the error in the 
native scroller.


But you can count me as another one who would like to see easier scroller 
implementation on mobile.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On June 1, 2021 3:15:07 PM Richard Gaskin via use-livecode 
 wrote:



Alternatively, you could handle your layout the way most apps on your
phone do, with responsive design.


1. Add this to your stack script:

on ResizeCommon x,y
   -- Header:
   set the rect of grc ID 1003 to 0,0,x,92
   set the rect of fld ID 1005 to 0,19,x,90
   --
   -- Footer:
   set the rect of widget "navigation" to 0,y-57, x, y
end ResizeCommon



2. Add this to cd 1 after grouping your buttons:

on resizeStack x,y
   ResizeCommon x,y -- see stack script
   set the loc of grp "btns" to item 1 of the loc of this cd, \
 item 2 of the loc of this cd + 20
end resizeStack



3. Add this to cd 2:

on resizeStack x,y
   ResizeCommon x,y -- see stack script
   set the rect of fld "spielanleitung" to 0, \
 the bottom of grp "top", \
 x, the top of grp "navibar"
   scrollererstellen
end resizeStack


This quickie responsive setup took me about 5 minutes, less time than
spent working around the bug, and now with a UI that works on all device
types and screen ratios, with fixed predictable control sizes, and no
cropping, padding, or distortion.

Bonus: Another few minutes on the cd 1 buttons group would even allow
both orientations to be supported.


Play with the resizing right in the IDE here:
go url "http://fourthworld.net/lc/scrollbugRD.livecode;

--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode





___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread Richard Gaskin via use-livecode 

Klaus wrote:

> Am 01.06.2021 um 22:49 schrieb Richard Gaskin:
>> No worries. All GUI OSes have had resizable windows since 1984.
>> If you've ever scripted for them on the desktop you already have
>> 90% of the habits needed to do the same on mobile.
>
> I never needed to do so in the last 21 years! :-D

I'm glad you mentioned that.

Resizable windows have been such a staple in software for so long, and 
so well supported in MetaCard, SuperCard, Toolbook, Gain, and most other 
GUI scripting tools, I've just taken for granted that anyone who's been 
in the biz for a while has written plenty of resizeStack handlers.


But I've been learning recently that's not the case. A lot of very 
experienced scripters have worked with dialogs, palettes, fixed-sized 
windows, and all manner of menus, but somehow have never been asked to 
make an app with resizable windows.


If I ever get around to writing an article on resizing strategies I'll 
keep that in mind.  Helpful to learn about one more xTalk veteran in the 
same boat.


--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread Klaus major-k via use-livecode 
Hi Richard,

> Am 01.06.2021 um 22:49 schrieb Richard Gaskin via use-livecode 
> :
> Klaus wrote:
>> >> This quickie responsive setup took me about 5 minutes, less time
>> >> than spent working around the bug, and now with a UI that works
>> >> on all device types and screen ratios, with fixed predictable control
>> >> sizes, and no cropping, padding, or distortion.
>> > yes, thank you, but please bear with me, this is my very first mobile
>> > app after owning my first cell phone for a couple of weeks. 8-)
> No worries. All GUI OSes have had resizable windows since 1984.
> If you've ever scripted for them on the desktop you already have 90% of the 
> habits needed to do the same on mobile.

I never needed to do so in the last 21 years! :-D

>> >> Bonus: Another few minutes on the cd 1 buttons group would even allow 
>> >> both orientations to be supported.
>> >
>> > Not neccessary for this app.
>> > But as a bonus I'd rather see this bug fixed. ;-)
> Indeed.
> I'm still wondering why we're still scripting scroll regions at all.
> If the engine knows which objects it considers scrollable, and it knows how 
> to provide access to OS handling of those interactions, put one engine 
> capability with the other and scripters are liberated from this silly 
> needless (and tragically LC-specific) tedium forever.

Yes, there are some areas where the enigne could liberate us from some tedious 
and in 2021 so unneccessary scripting.

> I'm also wondering why I'm alone in wondering that...

I bet you are NOT alone, at least I am with you!

> -- 
> Richard Gaskin

Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread Richard Gaskin via use-livecode 

Klaus wrote:

>> This quickie responsive setup took me about 5 minutes, less time
>> than spent working around the bug, and now with a UI that works
>> on all device types and screen ratios, with fixed predictable control
>> sizes, and no cropping, padding, or distortion.
>
> yes, thank you, but please bear with me, this is my very first mobile
> app after owning my first cell phone for a couple of weeks. 8-)

No worries. All GUI OSes have had resizable windows since 1984. If 
you've ever scripted for them on the desktop you already have 90% of the 
habits needed to do the same on mobile.



>> Bonus: Another few minutes on the cd 1 buttons group would even 
allow both orientations to be supported.

>
> Not neccessary for this app.
> But as a bonus I'd rather see this bug fixed. ;-)

Indeed.

I'm still wondering why we're still scripting scroll regions at all.

If the engine knows which objects it considers scrollable, and it knows 
how to provide access to OS handling of those interactions, put one 
engine capability with the other and scripters are liberated from this 
silly needless (and tragically LC-specific) tedium forever.


I'm also wondering why I'm alone in wondering that...

--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.com




___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread Klaus major-k via use-livecode 
Hi Richard,

> Am 01.06.2021 um 22:12 schrieb Richard Gaskin via use-livecode 
> :
> 
> Alternatively, you could handle your layout the way most apps on your phone 
> do, with responsive design.
> 
> 1. Add this to your stack script:
> ...
> This quickie responsive setup took me about 5 minutes, less time than spent 
> working around the bug, and now with a UI that works on all device types and 
> screen ratios, with fixed predictable control sizes, and no cropping, 
> padding, or distortion.

yes, thank you, but please bear with me, this is my very first mobile app after 
owning my first cell phone for a couple of weeks. 8-)

> Bonus: Another few minutes on the cd 1 buttons group would even allow both 
> orientations to be supported.

Not neccessary for this app.
But as a bonus I'd rather see this bug fixed. ;-)

> Play with the resizing right in the IDE here:
> go url "http://fourthworld.net/lc/scrollbugRD.livecode;
> 
> -- 
> Richard Gaskin
> Fourth World Systems
> Software Design and Development for the Desktop, Mobile, and the Web

Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread Richard Gaskin via use-livecode 
Alternatively, you could handle your layout the way most apps on your 
phone do, with responsive design.



1. Add this to your stack script:

on ResizeCommon x,y
   -- Header:
   set the rect of grc ID 1003 to 0,0,x,92
   set the rect of fld ID 1005 to 0,19,x,90
   --
   -- Footer:
   set the rect of widget "navigation" to 0,y-57, x, y
end ResizeCommon



2. Add this to cd 1 after grouping your buttons:

on resizeStack x,y
   ResizeCommon x,y -- see stack script
   set the loc of grp "btns" to item 1 of the loc of this cd, \
 item 2 of the loc of this cd + 20
end resizeStack



3. Add this to cd 2:

on resizeStack x,y
   ResizeCommon x,y -- see stack script
   set the rect of fld "spielanleitung" to 0, \
 the bottom of grp "top", \
 x, the top of grp "navibar"
   scrollererstellen
end resizeStack


This quickie responsive setup took me about 5 minutes, less time than 
spent working around the bug, and now with a UI that works on all device 
types and screen ratios, with fixed predictable control sizes, and no 
cropping, padding, or distortion.


Bonus: Another few minutes on the cd 1 buttons group would even allow 
both orientations to be supported.



Play with the resizing right in the IDE here:
go url "http://fourthworld.net/lc/scrollbugRD.livecode;

--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread J. Landman Gay via use-livecode 

On 6/1/21 1:55 PM, Klaus major-k via use-livecode wrote:

And "of empty" means with NO fullscreenmode, I guess?

Tried that, no die!
The dictionary tells me about "fullscreenmode":
...
• empty - The stack is resized (not scaled) to fit the screen.
(default) This is the legacy behavior.
...


Setting fullScreenMode to empty is the same as not using FSM at all; it's the old behavior we 
had before FSM was available. I think "of" was an autocomplete error; should be "to empty."



Maybe I am misunderstanding this, but my stack was cut off on the right and 
bottom
when setting FSM to EMPTY.

Dimensions of my stack are smaller than my devide!
Stack: 800*400
Device: 1280*720


I believe the resolution of the device also affects the stack size, so if the resolution of 
your phone is different than the resolution of your desktop then it will size the stack 
differently. But I'm not sure how the calculations work exactly.



It's either the Flying Spaghetti Monster


I highly doubt that! :-D


Off topic: a few years ago, a guy here in the U.S. went to renew his driver's license wearing a 
colander on his head. He said it was apparel for his deeply-held FSM Pastafarian religious 
beliefs, and they let him keep it on for the photo. Since then a few others have done the same. 
Permission depends on the state.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread Brian Milby via use-livecode 
Ok.  I’ll just pull down your demo and play around with it.

Sent from my iPhone

> On Jun 1, 2021, at 2:56 PM, Klaus major-k via use-livecode 
>  wrote:
> 
> Hi Jaques,
> 
>>> Am 01.06.2021 um 20:38 schrieb J. Landman Gay via use-livecode 
>>> :
>>> 
>>> Sorry, no idea what "FSM of empty" might be? :-)
>> 
>> It's either the Flying Spaghetti Monster
> 
> I highly doubt that! :-D
> 
>> or fullscreenmode. ;)
> 
> Makes sense, thanks!
> And "of empty" means with NO fullscreenmode, I guess?
> 
> Tried that, no die!
> The dictionary tells me about "fullscreenmode":
> ...
> • empty - The stack is resized (not scaled) to fit the screen. 
> (default) This is the legacy behavior.
> ...
> 
> Maybe I am misunderstanding this, but my stack was cut off on the right and 
> bottom
> when setting FSM to EMPTY.
> 
> Dimensions of my stack are smaller than my devide!
> Stack: 800*400
> Device: 1280*720
> 
> Is the dictionary wrong or do I miss or misunderstand something important?
> 
>> --
>> Jacqueline Landman Gay | jac...@hyperactivesw.com
> 
> Best
> 
> Klaus
> 
> --
> Klaus Major
> https://www.major-k.de
> https://www.major-k.de/bass
> kl...@major-k.de
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread Klaus major-k via use-livecode 
Hi Jaques,

> Am 01.06.2021 um 20:38 schrieb J. Landman Gay via use-livecode 
> :
> 
>> Sorry, no idea what "FSM of empty" might be? :-)
> 
> It's either the Flying Spaghetti Monster

I highly doubt that! :-D

> or fullscreenmode. ;)

Makes sense, thanks!
And "of empty" means with NO fullscreenmode, I guess?

Tried that, no die!
The dictionary tells me about "fullscreenmode":
...
• empty - The stack is resized (not scaled) to fit the screen. 
(default) This is the legacy behavior.
...

Maybe I am misunderstanding this, but my stack was cut off on the right and 
bottom
when setting FSM to EMPTY.

Dimensions of my stack are smaller than my devide!
Stack: 800*400
Device: 1280*720

Is the dictionary wrong or do I miss or misunderstand something important?

> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com

Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread J. Landman Gay via use-livecode 

Sorry, no idea what "FSM of empty" might be? :-)


It's either the Flying Spaghetti Monster or fullscreenmode. ;)

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On June 1, 2021 1:16:13 PM Klaus major-k via use-livecode 
 wrote:



Hi Brian,

Am 01.06.2021 um 17:09 schrieb Brian Milby via use-livecode 
:


One thing to try for testing would be to use FSM of empty


Sorry, no idea what "FSM of empty" might be? :-)


and see how many lines are required.


Will do, once I know what it means!

One thing I noticed with browser widget is that native elements render at 
device resolution inside regardless of FSM in use.  If it requires the 
same, then this is probably not related.  If the number changes, then I may 
be on to something.  In either case, having to fudge the height of a text 
field is not good.


Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode





___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread Klaus major-k via use-livecode 
Hi Brian,

> Am 01.06.2021 um 17:09 schrieb Brian Milby via use-livecode 
> :
> 
> One thing to try for testing would be to use FSM of empty

Sorry, no idea what "FSM of empty" might be? :-)

> and see how many lines are required.  

Will do, once I know what it means!

> One thing I noticed with browser widget is that native elements render at 
> device resolution inside regardless of FSM in use.  If it requires the same, 
> then this is probably not related.  If the number changes, then I may be on 
> to something.  In either case, having to fudge the height of a text field is 
> not good.

Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread Brian Milby via use-livecode 
One thing to try for testing would be to use FSM of empty and see how many 
lines are required.  One thing I noticed with browser widget is that native 
elements render at device resolution inside regardless of FSM in use.  If it 
requires the same, then this is probably not related.  If the number changes, 
then I may be on to something.  In either case, having to fudge the height of a 
text field is not good.

Sent from my iPhone

> On Jun 1, 2021, at 11:00 AM, Klaus major-k via use-livecode 
>  wrote:
> 
> Hi Rick,
> 
>> Am 01.06.2021 um 16:38 schrieb Rick Harrison via use-livecode 
>> :
>> Hi Klaus,
>> What happens if you add 100 blank lines?
> 
> I get the white space of hundred empty lines in the scroller.
> 
>> What happens if you add 100 blank lines and the last one has something on it?
> 
> Did not try that.
> 
>> I hope you find a suitable workaround because that’s a serious bug!
> 
> Hm, not sure, but it looks like you need at least 5 empty lines to "fool" LC 
> to compute 
> the correct scroll of the native scroller. Means all lines are visible, but 
> not the EMPTY lines!?
> 
> And yes, this IS a serious bug!
> 
>> Rick
> 
> Best
> 
> Klaus
> 
> --
> Klaus Major
> https://www.major-k.de
> https://www.major-k.de/bass
> kl...@major-k.de
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread Klaus major-k via use-livecode 
Hi Jaques,

> Am 01.06.2021 um 18:26 schrieb J. Landman Gay via use-livecode 
> :
> 
> I usually put one empty line at the end of the field and increase the native 
> scroller content height by twice
> or three times the textheight of the field. The amount of extra space 
> required in the scroller depends on
> the text size and textheight.

five empty lines solve my current problem.

> I think the problem is an incorrect calculation of the formattedHeight of the 
> field or group. BTW, did you group the field?

Sure! :-)
I even added a white button BELOW that field in the group, no dice!?

> It won't scroll smoothly unless you do, and the group should scroll rather 
> than the field.
> The field inside the group should be sized to its full height with its top 
> aligned to the top of the group.

It is.

> Set the group margins to 0

I did.

> and the layermode of the group to "scrolling".

I did NOT! Will try...

Tested, no difference in the end.

> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com

Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread J. Landman Gay via use-livecode 
I usually put one empty line at the end of the field and increase the 
native scroller content height by twice or three times the textheight of 
the field. The amount of extra space required in the scroller depends on 
the text size and textheight.


I think the problem is an incorrect calculation of the formattedHeight of 
the field or group. BTW, did you group the field? It won't scroll smoothly 
unless you do, and the group should scroll rather than the field. The field 
inside the group should be sized to its full height with its top aligned to 
the top of the group. Set the group margins to 0 and the layermode of the 
group to "scrolling".


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On June 1, 2021 10:01:33 AM Klaus major-k via use-livecode 
 wrote:
Hm, not sure, but it looks like you need at least 5 empty lines to "fool" 
LC to compute
the correct scroll of the native scroller. Means all lines are visible, but 
not the EMPTY lines!?




___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread Klaus major-k via use-livecode 
Hi Rick,

> Am 01.06.2021 um 16:38 schrieb Rick Harrison via use-livecode 
> :
> 
> Hi Klaus,
> 
> What happens if you add 100 blank lines?

I get the white space of hundred empty lines in the scroller.

> What happens if you add 100 blank lines and the last one has something on it?

Did not try that.

> I hope you find a suitable workaround because that’s a serious bug!

Hm, not sure, but it looks like you need at least 5 empty lines to "fool" LC to 
compute 
the correct scroll of the native scroller. Means all lines are visible, but not 
the EMPTY lines!?

And yes, this IS a serious bug!

> Rick

Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread Rick Harrison via use-livecode 
Hi Klaus,

What happens if you add 100 blank lines?

What happens if you add 100 blank lines and the last one has something on it?

I hope you find a suitable workaround because that’s a serious bug!

Rick

> On Jun 1, 2021, at 7:14 AM, Klaus major-k via use-livecode 
>  wrote:
> 
> Hi friends,
> 
> are there any (working!) workaround for this pesty bug where
> a correctly set up native scroller does not show the last line(s)?
> 
> Bug #: 
> 
> 
> I am really suprised that noone has noticed resp. reported this
> before, since this is a real showstopper in my opinion. :-/
> 
> OK, there is a special workaround on GITHUB for a stack of SWAMIs
> but this does not help in my current situation.
> 
> Any hints highly appreciated!
> 
> 
> Best
> 
> Klaus
> --
> Klaus Major
> https://www.major-k.de
> https://www.major-k.de/bass
> kl...@major-k.de
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread Klaus major-k via use-livecode 
Hi Brian,

> Am 01.06.2021 um 14:58 schrieb Brian Milby via use-livecode 
> :
> 
> I’ll need to build a test project this evening to reproduce using your full 
> screen mode.  So far I have only used “empty” with a scroller.  Hopefully 
> someone else will have more to suggest before then.

take my test stack from the quality database here:


I used this to test...

> Thanks,
> Brian

Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread Brian Milby via use-livecode 
I’ll need to build a test project this evening to reproduce using your full 
screen mode.  So far I have only used “empty” with a scroller.  Hopefully 
someone else will have more to suggest before then.

Thanks,
Brian

Sent from my iPhone

> On Jun 1, 2021, at 8:50 AM, Klaus major-k via use-livecode 
>  wrote:
> 
> Hi Brian,
> 
>> Am 01.06.2021 um 13:57 schrieb Brian Milby via use-livecode 
>> :
>> 
>> Which full screen mode are you using?
>> The referenced fix works by extending the scroll region longer than the 
>> actual content with a goal of allowing you to get to the last line.  What 
>> are you seeing when you try to use that?  (Does it let you get any further 
>> or just doesn’t change it at all for you?)
> 
> at the end of my field I added:
> ...
> EMPTY line
> --
> Another empty line
> 
> 
> I tested with an offset of 60 and 100:
> ...
> put 0,0,(the formattedWidth of group "scrollgroup"),(the formattedHeight of 
> group "scrollgroup" + 100) into tContentRect
> ...
> These last lines are never displayed/scrolled to!?
> So now what?
> 
> 
> Best
> 
> Klaus
> --
> Klaus Major
> https://www.major-k.de
> https://www.major-k.de/bass
> kl...@major-k.de
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread Klaus major-k via use-livecode 
Hi Brian,

> Am 01.06.2021 um 13:57 schrieb Brian Milby via use-livecode 
> :
> 
> Which full screen mode are you using?
> The referenced fix works by extending the scroll region longer than the 
> actual content with a goal of allowing you to get to the last line.  What are 
> you seeing when you try to use that?  (Does it let you get any further or 
> just doesn’t change it at all for you?)

at the end of my field I added:
...
EMPTY line
--
Another empty line


I tested with an offset of 60 and 100:
...
put 0,0,(the formattedWidth of group "scrollgroup"),(the formattedHeight of 
group "scrollgroup" + 100) into tContentRect
...
These last lines are never displayed/scrolled to!?
So now what?


Best

Klaus
--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread Klaus major-k via use-livecode 
Hi Brian,

> Am 01.06.2021 um 13:57 schrieb Brian Milby via use-livecode 
> :
> 
> Which full screen mode are you using?

on my device: exactfit

> The referenced fix works by extending the scroll region longer than the 
> actual content with a goal of allowing you to get to the last line.  
> What are you seeing when you try to use that?  (Does it let you get any 
> further or just doesn’t change it at all for you?)

Will try that and get back to you, thanks.


Best

Klaus
--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: workaround for cut-off text in native scroller?

2021-06-01 Thread Brian Milby via use-livecode 
Which full screen mode are you using?
The referenced fix works by extending the scroll region longer than the actual 
content with a goal of allowing you to get to the last line.  What are you 
seeing when you try to use that?  (Does it let you get any further or just 
doesn’t change it at all for you?)

Sent from my iPhone

> On Jun 1, 2021, at 7:16 AM, Klaus major-k via use-livecode 
>  wrote:
> 
> Hi friends,
> 
> are there any (working!) workaround for this pesty bug where
> a correctly set up native scroller does not show the last line(s)?
> 
> Bug #: 
> 
> 
> I am really suprised that noone has noticed resp. reported this
> before, since this is a real showstopper in my opinion. :-/
> 
> OK, there is a special workaround on GITHUB for a stack of SWAMIs
> but this does not help in my current situation.
> 
> Any hints highly appreciated!
> 
> 
> Best
> 
> Klaus
> --
> Klaus Major
> https://www.major-k.de
> https://www.major-k.de/bass
> kl...@major-k.de
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode