gxcor4415f96te8stny5kqws9
--Andrew Bell
From: Sannyasin Brahmanathaswami
Subject: Re: iOS scrollers
Perhaps I misunderstand you, but IMHO, "it not rocket science"
Regardless of the device or fullscreenmode. I use (and I think jacque
uses) the card rect?
If we set a scroller to the
.5 ITEMS
set the fullscreenMode of me to EMPTY // WORKS
You can download my sample stack from:
https colon slash slash
iu dot box dot com
slash s slash
sj3lca0gxcor4415f96te8stny5kqws9
--Andrew Bell
From: Sannyasin Brahmanathaswami
Subject: Re: iOS scrollers
Perhaps I misunderstand you, but
Hello all,
I believe I have found a workaround to this issue - please see the bug
report.
Kind regards,
Panos
--
On Mon, 2 Dec 2019 at 10:07, Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
> We shouldn't be scripting scrollers.
>
> If the control we placed on the card s
We shouldn't be scripting scrollers.
If the control we placed on the card scrolls, it should scroll. Doesn't
matter if it's Mac or Windows or Linux. Shouldn't matter if it's iOS or
Android.
Manually typing an interaction overlay is bizarre savagery better left
for those with a typing fetis
The bug number is the one Panos posted :
https://quality.livecode.com/show_bug.cgi?id=21456
You could add yourself to the cc list to track it.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On December 1, 2019 8:50:12 AM Sannyasin Brahmana
Thanks Alan, but it doesn't really. Some of my text fields already have a
couple of carriage returns after them as an attempt to fix another issue
and they also have the same problem. But if the bug is what
scrollerDidScroll returns, the length of the field probably doesn't matter.
I do appre
Hi Jacque,
Does putting a CR at the end of the field contents help? Before making the
mobile scroller etc.
I think that was a workaround I came up with ages ago for the same (/similar?)
problem. But could be that I'm misunderstanding your issue...
cheers
Alan
On 2 Dec 2019, at 3:30 am, J. La
That's exactly it, thanks Panos. I'd searched for formattedHeight and only
found my older bug so I added a comment there, but the one you've
referenced is more accurate.
I didn't realize the problem was in the scrollerDidScroll parameters. I
need a workaround in the next 2 weeks if there isn't
Hi all,
@Jacque
This sounds like bug https://quality.livecode.com/show_bug.cgi?id=21456
Kind regards,
Panos
--
On Sun, 1 Dec 2019 at 17:13, Sannyasin Brahmanathaswami via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Perhaps I misunderstand you, but IMHO, "it not rocket science"
>
> Re
Perhaps I misunderstand you, but IMHO, "it not rocket science"
Regardless of the device or fullscreenmode. I use (and I think jacque uses) the
card rect…
If we set a scroller to the "formatterHeight", in any model or "mode" context,
the user should be able to scroll right to the bottom, and se
It would be good to have a simple stack to test that only is for showing the
problem. One thing I would look at is how you are measuring coordinates when
using ShowAll. With ShowAll and Portrait, of a card that is iPhone 4 sized,
zero Y is not at the top of the iPhone 5 screen. If you are findin
Bug: QA ticket #...?
I believe you will use the previously confirmed number?
Agreed, it’s has become "a blocker." Not that you cannot build the app. But any
TOC and Indices you will have in the app don't work, from the user point of
view. The last line will appear if you use scroll up, (keep yo
I am still wondering to read issues dealing with rendering layout issues on
mobile devices anno 2019 (almost 2020!).
In my opinion this should be an integrated part in the LiveCode engine. From my
own experience writing your own geometric routines is never perfect and it has
given me a lot of h
This is a blocker for us. Adding extra space to the contentRect doesn't
work, Swami tested it on a real iPhone 10 and it shows the same issues
as the simulator.
If anyone has a workaround I need it real soon now. Meanwhile I'll put
in a bug report.
On 11/30/19 8:46 PM, Sannyasin Brahmanatha
Ditto that here. I still have you with handler.
Ralph said he was added 20 the rect, so I did this.
put ("0,0," & (the formattedwidth of control pName) & "," & \
the formattedheight of control pName + 20) into tRect
But on iPhone X increasing by a generic "20" in not enough.
I don't think users
I have scrolers that work fine in a simulated iPhone 6 Plus (which is
what the card size is.) But in iPhone X the last one or two lines are
cut off so you can't scroll to the bottom of the text. This happens
everywhere in the app where there's a scroller involved.
Why?
--
Jacqueline Landman G
Hi there,
I have two iOS scrollers in my app on the same card.
They almost work fine. They do scroll and show content but two
scrollers scroll at the same time.
What do I have to do to prevent this?
Do I add the same code (different id) to scrollToTop and scrollerDidScroll
This my code:
on
17 matches
Mail list logo
