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
> 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
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
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
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
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
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
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
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.
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
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
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
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,
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
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.
...
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
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
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
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
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
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
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
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
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,
>
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
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
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
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.
>
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
29 matches
Mail list logo
