Re: Help needed :)

2020-10-19 Thread panagiotis merakos via use-livecode
Great, thank you very much Matthias :)

I will file an enhancement request to make sure this behavior is documented
in the dictionary entry of the screenrect.

Kind regards,
Panos
--

On Mon, 19 Oct 2020 at 18:45, matthias rebbe via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Hi Panos,
>
> my father in law came back earlier than expected.
> You were correct. The phone display was zoomed.
> I switched it back to "standard" and tested again.
>
> With "standard" the screenrect returns  0,0,414,736
>
> Regards,
> Matthias
>
> -
> Matthias Rebbe
> Life Is Too Short For Boring Code
>
> > Am 19.10.2020 um 17:34 schrieb matthias rebbe via use-livecode <
> use-livecode@lists.runrev.com>:
> >
> >
> > -
> > Matthias Rebbe
> > Life Is Too Short For Boring Code
> >
> >> Am 19.10.2020 um 17:17 schrieb panagiotis merakos via use-livecode <
> use-livecode@lists.runrev.com >:
> >>
> >> Hmm I think I have found something - I had checked for this before -
> but in
> >> the wrong place.
> >>
> >> @Matthias could you check if "Display Zoom" is enabled in your device?
> >>
> >> This is in Settings -> Display and Brightness  and then scroll down and
> in
> >> the "Display Zoom" section, does it say "Standard" or "Zoomed" ?
> >>
> > Believe me or not, that was something i thought also could be the
> culprit. But forgot to test, because i got an important phone call.
> >
> > I will test this later today. I had to give the phone back to the owner,
> but can get it back in the evening.
> >
> > Regards,
> > Matthias
> >
> >
> >> Kind regards,
> >> Panos
> >> --
> >>
> >> On Mon, 19 Oct 2020 at 17:51, panagiotis merakos 
> wrote:
> >>
> >>> Hello Matthias,
> >>>
> >>> Thank you very much for testing. Hmm that's interesting. I forgot to
> >>> mention that the affected iPhones 8+ are running iOS 14.
> >>>
> >>> The simulator we tested was running iOS 13.3. I am wondering if this
> is an
> >>> iOS 14 issue.
> >>>
> >>> We are working on adding support for building with Xcode 12 / iOS 14
> SDK,
> >>> so once this is ready, I'll test on the iOS 14 simulator.
> >>>
> >>> In the meantime, if anyone has an iPhone 6+/7+/8+ running iOS < 14 and
> >>> would like to check what "the screenrect" returns, it would be great :)
> >>>
> >>> Kind regards,
> >>> Panos
> >>> --
> >>>
> >>>
> >>> On Mon, 19 Oct 2020 at 17:24, matthias rebbe via use-livecode <
> >>> use-livecode@lists.runrev.com> wrote:
> >>>
>  Hi Panos,
> 
>  i just borrowed me an iphone 8 Plus.  I can confirm that on the real
>  device the screenrect returns 0,0,375,667
>  Tried with all 3 variations (ipad, ipod, ipod/iphone/ipad) and
>  with iOS 10,11,12,13.
> 
>  iOS 14.01
>  Modell MQ8L2ZD/A
> 
> 
>  Regards,
> 
> 
>  -
>  Matthias Rebbe
>  Life Is Too Short For Boring Code
> 
> > Am 19.10.2020 um 14:43 schrieb panagiotis merakos via use-livecode <
>  use-livecode@lists.runrev.com>:
> >
> > Heh I wrote that msg in my phone while I was in a hurry, and I now
> see
>  the
> > auto-correct has changed a couple of things :)
> >
> > Corrections:
> >
> > * A LC user ...
> >
> > * ...and it works as expected for us
> >
> > Thank you :)
> >
> > Panos
> > --
> >
> > On Mon, 19 Oct 2020 at 14:58, panagiotis merakos <
>  panos.mera...@livecode.com >
> > wrote:
> >
> >> Hello folks,
> >>
> >> I LC user (or in fact a couple of this user's clients) are
>  experiencing a
> >> strange issue which we cannot reproduce, as we do not have the
> specific
> >> hardware.
> >>
> >> Long story short, "the screenrect" function returns for them
> incorrect
> >> values on an iPhone 8 Plus physical device. We have tested in the
>  iPhone 8
> >> Plus simulator and it world as expected for us.
> >>
> >> More specifically, the screenrect() returns 0,0,375,667 (which is
> the
> >> screenrect of iPhone8) instead of 0,0,414,736 (which is the
> screenrect
>  of
> >> iPhone 8 Plus.
> >>
> >> Do you have such a device and if yes, would it be possible to do a
>  quick
> >> test and report here what you get?
> >>
> >> Thanks a lot :)
> >>
> >> Kind regards,
> >> Panos
> >>
> >> PS: I guess an iPhone 6 Plus or iPhone 7 Plus will do too, as all
>  these 3
> >> devices have the same screen size.
> >> --
> >>
> >>
> >>
> >
> > --
> > Panagiotis Merakos   panos.mera...@livecode.com>>
> > LiveCode Software Developer
> >
> > Everyone Can Create Apps  https://livecode.com/>>
> > ___
> > use-livecode mailing list
> > use-livecode@lists.runrev.com 
> > Please visit this url to subscribe, unsubscribe and manage your

Re: Help needed :)

2020-10-19 Thread matthias rebbe via use-livecode
Hi Panos,

my father in law came back earlier than expected.
You were correct. The phone display was zoomed.
I switched it back to "standard" and tested again.

With "standard" the screenrect returns  0,0,414,736

Regards,
Matthias

-
Matthias Rebbe
Life Is Too Short For Boring Code

> Am 19.10.2020 um 17:34 schrieb matthias rebbe via use-livecode 
> :
> 
> 
> -
> Matthias Rebbe
> Life Is Too Short For Boring Code
> 
>> Am 19.10.2020 um 17:17 schrieb panagiotis merakos via use-livecode 
>> mailto:use-livecode@lists.runrev.com>>:
>> 
>> Hmm I think I have found something - I had checked for this before - but in
>> the wrong place.
>> 
>> @Matthias could you check if "Display Zoom" is enabled in your device?
>> 
>> This is in Settings -> Display and Brightness  and then scroll down and in
>> the "Display Zoom" section, does it say "Standard" or "Zoomed" ?
>> 
> Believe me or not, that was something i thought also could be the culprit. 
> But forgot to test, because i got an important phone call.
> 
> I will test this later today. I had to give the phone back to the owner, but 
> can get it back in the evening.
> 
> Regards,
> Matthias
> 
> 
>> Kind regards,
>> Panos
>> --
>> 
>> On Mon, 19 Oct 2020 at 17:51, panagiotis merakos  wrote:
>> 
>>> Hello Matthias,
>>> 
>>> Thank you very much for testing. Hmm that's interesting. I forgot to
>>> mention that the affected iPhones 8+ are running iOS 14.
>>> 
>>> The simulator we tested was running iOS 13.3. I am wondering if this is an
>>> iOS 14 issue.
>>> 
>>> We are working on adding support for building with Xcode 12 / iOS 14 SDK,
>>> so once this is ready, I'll test on the iOS 14 simulator.
>>> 
>>> In the meantime, if anyone has an iPhone 6+/7+/8+ running iOS < 14 and
>>> would like to check what "the screenrect" returns, it would be great :)
>>> 
>>> Kind regards,
>>> Panos
>>> --
>>> 
>>> 
>>> On Mon, 19 Oct 2020 at 17:24, matthias rebbe via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
>>> 
 Hi Panos,
 
 i just borrowed me an iphone 8 Plus.  I can confirm that on the real
 device the screenrect returns 0,0,375,667
 Tried with all 3 variations (ipad, ipod, ipod/iphone/ipad) and
 with iOS 10,11,12,13.
 
 iOS 14.01
 Modell MQ8L2ZD/A
 
 
 Regards,
 
 
 -
 Matthias Rebbe
 Life Is Too Short For Boring Code
 
> Am 19.10.2020 um 14:43 schrieb panagiotis merakos via use-livecode <
 use-livecode@lists.runrev.com>:
> 
> Heh I wrote that msg in my phone while I was in a hurry, and I now see
 the
> auto-correct has changed a couple of things :)
> 
> Corrections:
> 
> * A LC user ...
> 
> * ...and it works as expected for us
> 
> Thank you :)
> 
> Panos
> --
> 
> On Mon, 19 Oct 2020 at 14:58, panagiotis merakos <
 panos.mera...@livecode.com >
> wrote:
> 
>> Hello folks,
>> 
>> I LC user (or in fact a couple of this user's clients) are
 experiencing a
>> strange issue which we cannot reproduce, as we do not have the specific
>> hardware.
>> 
>> Long story short, "the screenrect" function returns for them incorrect
>> values on an iPhone 8 Plus physical device. We have tested in the
 iPhone 8
>> Plus simulator and it world as expected for us.
>> 
>> More specifically, the screenrect() returns 0,0,375,667 (which is the
>> screenrect of iPhone8) instead of 0,0,414,736 (which is the screenrect
 of
>> iPhone 8 Plus.
>> 
>> Do you have such a device and if yes, would it be possible to do a
 quick
>> test and report here what you get?
>> 
>> Thanks a lot :)
>> 
>> Kind regards,
>> Panos
>> 
>> PS: I guess an iPhone 6 Plus or iPhone 7 Plus will do too, as all
 these 3
>> devices have the same screen size.
>> --
>> 
>> 
>> 
> 
> --
> Panagiotis Merakos >>> panos.mera...@livecode.com>>
> LiveCode Software Developer
> 
> Everyone Can Create Apps >
> ___
> 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 <
 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
 
>>> 
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your 

Re: Help needed :)

2020-10-19 Thread panagiotis merakos via use-livecode
Thanks Matthias, your help is much appreciated.

Kind regards
Panos

On Mon, Oct 19, 2020, 18:35 matthias rebbe via use-livecode <
use-livecode@lists.runrev.com> wrote:

>
> -
> Matthias Rebbe
> Life Is Too Short For Boring Code
>
> > Am 19.10.2020 um 17:17 schrieb panagiotis merakos via use-livecode <
> use-livecode@lists.runrev.com>:
> >
> > Hmm I think I have found something - I had checked for this before - but
> in
> > the wrong place.
> >
> > @Matthias could you check if "Display Zoom" is enabled in your device?
> >
> > This is in Settings -> Display and Brightness  and then scroll down and
> in
> > the "Display Zoom" section, does it say "Standard" or "Zoomed" ?
> >
> Believe me or not, that was something i thought also could be the culprit.
> But forgot to test, because i got an important phone call.
>
> I will test this later today. I had to give the phone back to the owner,
> but can get it back in the evening.
>
> Regards,
> Matthias
>
>
> > Kind regards,
> > Panos
> > --
> >
> > On Mon, 19 Oct 2020 at 17:51, panagiotis merakos 
> wrote:
> >
> >> Hello Matthias,
> >>
> >> Thank you very much for testing. Hmm that's interesting. I forgot to
> >> mention that the affected iPhones 8+ are running iOS 14.
> >>
> >> The simulator we tested was running iOS 13.3. I am wondering if this is
> an
> >> iOS 14 issue.
> >>
> >> We are working on adding support for building with Xcode 12 / iOS 14
> SDK,
> >> so once this is ready, I'll test on the iOS 14 simulator.
> >>
> >> In the meantime, if anyone has an iPhone 6+/7+/8+ running iOS < 14 and
> >> would like to check what "the screenrect" returns, it would be great :)
> >>
> >> Kind regards,
> >> Panos
> >> --
> >>
> >>
> >> On Mon, 19 Oct 2020 at 17:24, matthias rebbe via use-livecode <
> >> use-livecode@lists.runrev.com> wrote:
> >>
> >>> Hi Panos,
> >>>
> >>> i just borrowed me an iphone 8 Plus.  I can confirm that on the real
> >>> device the screenrect returns 0,0,375,667
> >>> Tried with all 3 variations (ipad, ipod, ipod/iphone/ipad) and
> >>> with iOS 10,11,12,13.
> >>>
> >>> iOS 14.01
> >>> Modell MQ8L2ZD/A
> >>>
> >>>
> >>> Regards,
> >>>
> >>>
> >>> -
> >>> Matthias Rebbe
> >>> Life Is Too Short For Boring Code
> >>>
>  Am 19.10.2020 um 14:43 schrieb panagiotis merakos via use-livecode <
> >>> use-livecode@lists.runrev.com>:
> 
>  Heh I wrote that msg in my phone while I was in a hurry, and I now see
> >>> the
>  auto-correct has changed a couple of things :)
> 
>  Corrections:
> 
>  * A LC user ...
> 
>  * ...and it works as expected for us
> 
>  Thank you :)
> 
>  Panos
>  --
> 
>  On Mon, 19 Oct 2020 at 14:58, panagiotis merakos <
> >>> panos.mera...@livecode.com >
>  wrote:
> 
> > Hello folks,
> >
> > I LC user (or in fact a couple of this user's clients) are
> >>> experiencing a
> > strange issue which we cannot reproduce, as we do not have the
> specific
> > hardware.
> >
> > Long story short, "the screenrect" function returns for them
> incorrect
> > values on an iPhone 8 Plus physical device. We have tested in the
> >>> iPhone 8
> > Plus simulator and it world as expected for us.
> >
> > More specifically, the screenrect() returns 0,0,375,667 (which is the
> > screenrect of iPhone8) instead of 0,0,414,736 (which is the
> screenrect
> >>> of
> > iPhone 8 Plus.
> >
> > Do you have such a device and if yes, would it be possible to do a
> >>> quick
> > test and report here what you get?
> >
> > Thanks a lot :)
> >
> > Kind regards,
> > Panos
> >
> > PS: I guess an iPhone 6 Plus or iPhone 7 Plus will do too, as all
> >>> these 3
> > devices have the same screen size.
> > --
> >
> >
> >
> 
>  --
>  Panagiotis Merakos  >>> panos.mera...@livecode.com>>
>  LiveCode Software Developer
> 
>  Everyone Can Create Apps  >>
>  ___
>  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 <
> >>> 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
> >>>
> >>
> > ___
> > 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: Help needed :)

2020-10-19 Thread matthias rebbe via use-livecode


-
Matthias Rebbe
Life Is Too Short For Boring Code

> Am 19.10.2020 um 17:17 schrieb panagiotis merakos via use-livecode 
> :
> 
> Hmm I think I have found something - I had checked for this before - but in
> the wrong place.
> 
> @Matthias could you check if "Display Zoom" is enabled in your device?
> 
> This is in Settings -> Display and Brightness  and then scroll down and in
> the "Display Zoom" section, does it say "Standard" or "Zoomed" ?
> 
Believe me or not, that was something i thought also could be the culprit. But 
forgot to test, because i got an important phone call.

I will test this later today. I had to give the phone back to the owner, but 
can get it back in the evening.

Regards,
Matthias


> Kind regards,
> Panos
> --
> 
> On Mon, 19 Oct 2020 at 17:51, panagiotis merakos  wrote:
> 
>> Hello Matthias,
>> 
>> Thank you very much for testing. Hmm that's interesting. I forgot to
>> mention that the affected iPhones 8+ are running iOS 14.
>> 
>> The simulator we tested was running iOS 13.3. I am wondering if this is an
>> iOS 14 issue.
>> 
>> We are working on adding support for building with Xcode 12 / iOS 14 SDK,
>> so once this is ready, I'll test on the iOS 14 simulator.
>> 
>> In the meantime, if anyone has an iPhone 6+/7+/8+ running iOS < 14 and
>> would like to check what "the screenrect" returns, it would be great :)
>> 
>> Kind regards,
>> Panos
>> --
>> 
>> 
>> On Mon, 19 Oct 2020 at 17:24, matthias rebbe via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> 
>>> Hi Panos,
>>> 
>>> i just borrowed me an iphone 8 Plus.  I can confirm that on the real
>>> device the screenrect returns 0,0,375,667
>>> Tried with all 3 variations (ipad, ipod, ipod/iphone/ipad) and
>>> with iOS 10,11,12,13.
>>> 
>>> iOS 14.01
>>> Modell MQ8L2ZD/A
>>> 
>>> 
>>> Regards,
>>> 
>>> 
>>> -
>>> Matthias Rebbe
>>> Life Is Too Short For Boring Code
>>> 
 Am 19.10.2020 um 14:43 schrieb panagiotis merakos via use-livecode <
>>> use-livecode@lists.runrev.com>:
 
 Heh I wrote that msg in my phone while I was in a hurry, and I now see
>>> the
 auto-correct has changed a couple of things :)
 
 Corrections:
 
 * A LC user ...
 
 * ...and it works as expected for us
 
 Thank you :)
 
 Panos
 --
 
 On Mon, 19 Oct 2020 at 14:58, panagiotis merakos <
>>> panos.mera...@livecode.com >
 wrote:
 
> Hello folks,
> 
> I LC user (or in fact a couple of this user's clients) are
>>> experiencing a
> strange issue which we cannot reproduce, as we do not have the specific
> hardware.
> 
> Long story short, "the screenrect" function returns for them incorrect
> values on an iPhone 8 Plus physical device. We have tested in the
>>> iPhone 8
> Plus simulator and it world as expected for us.
> 
> More specifically, the screenrect() returns 0,0,375,667 (which is the
> screenrect of iPhone8) instead of 0,0,414,736 (which is the screenrect
>>> of
> iPhone 8 Plus.
> 
> Do you have such a device and if yes, would it be possible to do a
>>> quick
> test and report here what you get?
> 
> Thanks a lot :)
> 
> Kind regards,
> Panos
> 
> PS: I guess an iPhone 6 Plus or iPhone 7 Plus will do too, as all
>>> these 3
> devices have the same screen size.
> --
> 
> 
> 
 
 --
 Panagiotis Merakos >> panos.mera...@livecode.com>>
 LiveCode Software Developer
 
 Everyone Can Create Apps >
 ___
 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 <
>>> 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
>>> 
>> 
> ___
> 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: Help needed :)

2020-10-19 Thread panagiotis merakos via use-livecode
Hmm I think I have found something - I had checked for this before - but in
the wrong place.

@Matthias could you check if "Display Zoom" is enabled in your device?

This is in Settings -> Display and Brightness  and then scroll down and in
the "Display Zoom" section, does it say "Standard" or "Zoomed" ?

Kind regards,
Panos
--

On Mon, 19 Oct 2020 at 17:51, panagiotis merakos  wrote:

> Hello Matthias,
>
> Thank you very much for testing. Hmm that's interesting. I forgot to
> mention that the affected iPhones 8+ are running iOS 14.
>
> The simulator we tested was running iOS 13.3. I am wondering if this is an
> iOS 14 issue.
>
> We are working on adding support for building with Xcode 12 / iOS 14 SDK,
> so once this is ready, I'll test on the iOS 14 simulator.
>
> In the meantime, if anyone has an iPhone 6+/7+/8+ running iOS < 14 and
> would like to check what "the screenrect" returns, it would be great :)
>
> Kind regards,
> Panos
> --
>
>
> On Mon, 19 Oct 2020 at 17:24, matthias rebbe via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> Hi Panos,
>>
>> i just borrowed me an iphone 8 Plus.  I can confirm that on the real
>> device the screenrect returns 0,0,375,667
>> Tried with all 3 variations (ipad, ipod, ipod/iphone/ipad) and
>> with iOS 10,11,12,13.
>>
>> iOS 14.01
>> Modell MQ8L2ZD/A
>>
>>
>> Regards,
>>
>>
>> -
>> Matthias Rebbe
>> Life Is Too Short For Boring Code
>>
>> > Am 19.10.2020 um 14:43 schrieb panagiotis merakos via use-livecode <
>> use-livecode@lists.runrev.com>:
>> >
>> > Heh I wrote that msg in my phone while I was in a hurry, and I now see
>> the
>> > auto-correct has changed a couple of things :)
>> >
>> > Corrections:
>> >
>> > * A LC user ...
>> >
>> > * ...and it works as expected for us
>> >
>> > Thank you :)
>> >
>> > Panos
>> > --
>> >
>> > On Mon, 19 Oct 2020 at 14:58, panagiotis merakos <
>> panos.mera...@livecode.com >
>> > wrote:
>> >
>> >> Hello folks,
>> >>
>> >> I LC user (or in fact a couple of this user's clients) are
>> experiencing a
>> >> strange issue which we cannot reproduce, as we do not have the specific
>> >> hardware.
>> >>
>> >> Long story short, "the screenrect" function returns for them incorrect
>> >> values on an iPhone 8 Plus physical device. We have tested in the
>> iPhone 8
>> >> Plus simulator and it world as expected for us.
>> >>
>> >> More specifically, the screenrect() returns 0,0,375,667 (which is the
>> >> screenrect of iPhone8) instead of 0,0,414,736 (which is the screenrect
>> of
>> >> iPhone 8 Plus.
>> >>
>> >> Do you have such a device and if yes, would it be possible to do a
>> quick
>> >> test and report here what you get?
>> >>
>> >> Thanks a lot :)
>> >>
>> >> Kind regards,
>> >> Panos
>> >>
>> >> PS: I guess an iPhone 6 Plus or iPhone 7 Plus will do too, as all
>> these 3
>> >> devices have the same screen size.
>> >> --
>> >>
>> >>
>> >>
>> >
>> > --
>> > Panagiotis Merakos > panos.mera...@livecode.com>>
>> > LiveCode Software Developer
>> >
>> > Everyone Can Create Apps >
>> > ___
>> > 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 <
>> 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
>>
>
___
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: Help needed :)

2020-10-19 Thread panagiotis merakos via use-livecode
Hello Matthias,

Thank you very much for testing. Hmm that's interesting. I forgot to
mention that the affected iPhones 8+ are running iOS 14.

The simulator we tested was running iOS 13.3. I am wondering if this is an
iOS 14 issue.

We are working on adding support for building with Xcode 12 / iOS 14 SDK,
so once this is ready, I'll test on the iOS 14 simulator.

In the meantime, if anyone has an iPhone 6+/7+/8+ running iOS < 14 and
would like to check what "the screenrect" returns, it would be great :)

Kind regards,
Panos
--


On Mon, 19 Oct 2020 at 17:24, matthias rebbe via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Hi Panos,
>
> i just borrowed me an iphone 8 Plus.  I can confirm that on the real
> device the screenrect returns 0,0,375,667
> Tried with all 3 variations (ipad, ipod, ipod/iphone/ipad) and with
> iOS 10,11,12,13.
>
> iOS 14.01
> Modell MQ8L2ZD/A
>
>
> Regards,
>
>
> -
> Matthias Rebbe
> Life Is Too Short For Boring Code
>
> > Am 19.10.2020 um 14:43 schrieb panagiotis merakos via use-livecode <
> use-livecode@lists.runrev.com>:
> >
> > Heh I wrote that msg in my phone while I was in a hurry, and I now see
> the
> > auto-correct has changed a couple of things :)
> >
> > Corrections:
> >
> > * A LC user ...
> >
> > * ...and it works as expected for us
> >
> > Thank you :)
> >
> > Panos
> > --
> >
> > On Mon, 19 Oct 2020 at 14:58, panagiotis merakos <
> panos.mera...@livecode.com >
> > wrote:
> >
> >> Hello folks,
> >>
> >> I LC user (or in fact a couple of this user's clients) are experiencing
> a
> >> strange issue which we cannot reproduce, as we do not have the specific
> >> hardware.
> >>
> >> Long story short, "the screenrect" function returns for them incorrect
> >> values on an iPhone 8 Plus physical device. We have tested in the
> iPhone 8
> >> Plus simulator and it world as expected for us.
> >>
> >> More specifically, the screenrect() returns 0,0,375,667 (which is the
> >> screenrect of iPhone8) instead of 0,0,414,736 (which is the screenrect
> of
> >> iPhone 8 Plus.
> >>
> >> Do you have such a device and if yes, would it be possible to do a quick
> >> test and report here what you get?
> >>
> >> Thanks a lot :)
> >>
> >> Kind regards,
> >> Panos
> >>
> >> PS: I guess an iPhone 6 Plus or iPhone 7 Plus will do too, as all these
> 3
> >> devices have the same screen size.
> >> --
> >>
> >>
> >>
> >
> > --
> > Panagiotis Merakos  panos.mera...@livecode.com>>
> > LiveCode Software Developer
> >
> > Everyone Can Create Apps >
> > ___
> > 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 <
> 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
>
___
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: Help needed :)

2020-10-19 Thread matthias rebbe via use-livecode
Hi Panos,

i just borrowed me an iphone 8 Plus.  I can confirm that on the real device the 
screenrect returns 0,0,375,667
Tried with all 3 variations (ipad, ipod, ipod/iphone/ipad) and with iOS 
10,11,12,13.

iOS 14.01
Modell MQ8L2ZD/A


Regards,


-
Matthias Rebbe
Life Is Too Short For Boring Code

> Am 19.10.2020 um 14:43 schrieb panagiotis merakos via use-livecode 
> :
> 
> Heh I wrote that msg in my phone while I was in a hurry, and I now see the
> auto-correct has changed a couple of things :)
> 
> Corrections:
> 
> * A LC user ...
> 
> * ...and it works as expected for us
> 
> Thank you :)
> 
> Panos
> --
> 
> On Mon, 19 Oct 2020 at 14:58, panagiotis merakos  >
> wrote:
> 
>> Hello folks,
>> 
>> I LC user (or in fact a couple of this user's clients) are experiencing a
>> strange issue which we cannot reproduce, as we do not have the specific
>> hardware.
>> 
>> Long story short, "the screenrect" function returns for them incorrect
>> values on an iPhone 8 Plus physical device. We have tested in the iPhone 8
>> Plus simulator and it world as expected for us.
>> 
>> More specifically, the screenrect() returns 0,0,375,667 (which is the
>> screenrect of iPhone8) instead of 0,0,414,736 (which is the screenrect of
>> iPhone 8 Plus.
>> 
>> Do you have such a device and if yes, would it be possible to do a quick
>> test and report here what you get?
>> 
>> Thanks a lot :)
>> 
>> Kind regards,
>> Panos
>> 
>> PS: I guess an iPhone 6 Plus or iPhone 7 Plus will do too, as all these 3
>> devices have the same screen size.
>> --
>> 
>> 
>> 
> 
> -- 
> Panagiotis Merakos  >
> LiveCode Software Developer
> 
> Everyone Can Create Apps >
> ___
> 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: Help needed :)

2020-10-19 Thread panagiotis merakos via use-livecode
Heh I wrote that msg in my phone while I was in a hurry, and I now see the
auto-correct has changed a couple of things :)

Corrections:

* A LC user ...

* ...and it works as expected for us

Thank you :)

Panos
--

On Mon, 19 Oct 2020 at 14:58, panagiotis merakos 
wrote:

> Hello folks,
>
> I LC user (or in fact a couple of this user's clients) are experiencing a
> strange issue which we cannot reproduce, as we do not have the specific
> hardware.
>
> Long story short, "the screenrect" function returns for them incorrect
> values on an iPhone 8 Plus physical device. We have tested in the iPhone 8
> Plus simulator and it world as expected for us.
>
> More specifically, the screenrect() returns 0,0,375,667 (which is the
> screenrect of iPhone8) instead of 0,0,414,736 (which is the screenrect of
> iPhone 8 Plus.
>
> Do you have such a device and if yes, would it be possible to do a quick
> test and report here what you get?
>
> Thanks a lot :)
>
> Kind regards,
> Panos
>
> PS: I guess an iPhone 6 Plus or iPhone 7 Plus will do too, as all these 3
> devices have the same screen size.
> --
>
>
>

-- 
Panagiotis Merakos 
LiveCode Software Developer

Everyone Can Create Apps 
___
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: Help needed with a nasty bug

2017-08-04 Thread Mike Kerner via use-livecode
Can we have more info on the configurations of the folks seeing this?
Win version
Machine config
VM - Y/N, brand, version
___
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: Help needed with scaleFactor and scaling

2017-02-18 Thread Colin Holgate via use-livecode
This seems to work (to make button 1 appear to be 100 pixels from the top and 
left, and to appear to be 200 wide and 150 tall):

on fixit
   put random(10)/10 + 1 into it
   set the scalefactor of this stack to it
   set the rect of btn 1 to 100/it,100/it,100/it+100/it,100/it+50/it
end fixit



___
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: Help needed with ConvertXMLToArray

2015-03-18 Thread Richard Gaskin

Graham Samuel wrote:

 If you do a numeric sort by these numbers, 1000 will come before 9.

If a numeric sort produces that outcome either the data isn't purely 
numeric or you've found a bug.



 Without this, an XML file with child nodes in a certain order will
 end up in a different order when converted to an array - and an order
 that isn't that easy to modify at this point.

LiveCode's arrays are associative arrays, in which elements have no 
inherent order relative to one another.


Keys are associated with values by a hash that determines the memory 
location of the value, and like most hashes the result maintains no 
metadata which describes either insertion order or order relative to 
other key values.


We can access array elements with a sense of order by first obtaining 
the keys and sorting those in whatever way is needed for the task at 
hand (numeric, alphanumeric, dateTime, etc.; provided of course the sort 
command works as questioned above).


--
 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: Help needed: Shell script stopped working in Mountain Lion!

2012-08-26 Thread Mike Bonner
After poking around some on mountain lion it looks like convert is gone.
 If these are upgraded machines you might be able to locate it somewhere in
/Previous System/...

Not positive this is the issue but its worth a check, and I am sure that
convert is not in the location you specified on my system. (also did a find
/ -name convert to search the whole system and didn't locate it)

On Sun, Aug 26, 2012 at 3:08 PM, Bruce Pokras bruc...@comcast.net wrote:

 Hello all!

 I develop an application called Patent Grabber that downloads patents from
 various US and international patent authorities. Unlike many other
 authorities that provide patent pages in PDF, the US Patent  Trademark
 Office (USPTO) provides patent pages in TIFF. From Tiger through Lion, the
 following script (which I believe came from a member of this group) has
 worked to convert those TIFF images into PDF pages:

 put /System/Library/Printers/Libraries/convert into tConvertApp
 get shell(tConvertApp  -f  quote  tiffFile  quote  -o  quote
  pdfFile  quote  -j application/pdf 21)

 Now under Mountain Lion this script has stopped working. Users of my
 application who have upgraded to Mountain Lion are left with a folder full
 of TIFFs and an error message from my application that it could not find
 any PDFs to combine into the final single PDF patent file. Does anyone have
 an idea what could be happening?

 Since foreign patent authorities provide patent pages in PDF, I know that
 the other shell script that Patent Grabber uses (which combines multiple
 PDF pages into a single PDF file) works fine. I think that should rule out
 this being a Mountain Lion security issue as a result of my application
 being unsigned, right??? Everything is going on in the Documents folder.

 Any insights would be greatly appreciated. My 2006 iMac cannot run
 Mountain Lion, so I cannot simply do the upgrade to see what is going on.

 Regards,

 Bruce Pokras
 Blazing Dawn Software
 www.blazingdawn.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: Help needed: Shell script stopped working in Mountain Lion!

2012-08-26 Thread Matthias Rebbe
Bruce,

if i remember right, but i could be wrong, then convert was just a symlink for 
cupsfilter.

https://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man8/cupsfilter.8.html


Regards,

Matthias


Am 26.08.2012 um 23:08 schrieb Bruce Pokras bruc...@comcast.net:

 Hello all!
 
 I develop an application called Patent Grabber that downloads patents from 
 various US and international patent authorities. Unlike many other 
 authorities that provide patent pages in PDF, the US Patent  Trademark 
 Office (USPTO) provides patent pages in TIFF. From Tiger through Lion, the 
 following script (which I believe came from a member of this group) has 
 worked to convert those TIFF images into PDF pages:
 
 put /System/Library/Printers/Libraries/convert into tConvertApp
 get shell(tConvertApp  -f  quote  tiffFile  quote  -o  quote  
 pdfFile  quote  -j application/pdf 21)
 
 Now under Mountain Lion this script has stopped working. Users of my 
 application who have upgraded to Mountain Lion are left with a folder full of 
 TIFFs and an error message from my application that it could not find any 
 PDFs to combine into the final single PDF patent file. Does anyone have an 
 idea what could be happening?
 
 Since foreign patent authorities provide patent pages in PDF, I know that the 
 other shell script that Patent Grabber uses (which combines multiple PDF 
 pages into a single PDF file) works fine. I think that should rule out this 
 being a Mountain Lion security issue as a result of my application being 
 unsigned, right??? Everything is going on in the Documents folder.
 
 Any insights would be greatly appreciated. My 2006 iMac cannot run Mountain 
 Lion, so I cannot simply do the upgrade to see what is going on.
 
 Regards,
 
 Bruce Pokras
 Blazing Dawn Software
 www.blazingdawn.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: Help needed: Shell script stopped working in Mountain Lion!

2012-08-26 Thread Mike Bonner
Oh cool! Just read up on cupsfilter and it looks like you're right.

On Sun, Aug 26, 2012 at 4:14 PM, Matthias Rebbe 
matthias_livecode_150...@m-r-d.de wrote:

 Bruce,

 if i remember right, but i could be wrong, then convert was just a symlink
 for cupsfilter.


 https://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man8/cupsfilter.8.html


 Regards,

 Matthias


 Am 26.08.2012 um 23:08 schrieb Bruce Pokras bruc...@comcast.net:

  Hello all!
 
  I develop an application called Patent Grabber that downloads patents
 from various US and international patent authorities. Unlike many other
 authorities that provide patent pages in PDF, the US Patent  Trademark
 Office (USPTO) provides patent pages in TIFF. From Tiger through Lion, the
 following script (which I believe came from a member of this group) has
 worked to convert those TIFF images into PDF pages:
 
  put /System/Library/Printers/Libraries/convert into tConvertApp
  get shell(tConvertApp  -f  quote  tiffFile  quote  -o 
 quote  pdfFile  quote  -j application/pdf 21)
 
  Now under Mountain Lion this script has stopped working. Users of my
 application who have upgraded to Mountain Lion are left with a folder full
 of TIFFs and an error message from my application that it could not find
 any PDFs to combine into the final single PDF patent file. Does anyone have
 an idea what could be happening?
 
  Since foreign patent authorities provide patent pages in PDF, I know
 that the other shell script that Patent Grabber uses (which combines
 multiple PDF pages into a single PDF file) works fine. I think that should
 rule out this being a Mountain Lion security issue as a result of my
 application being unsigned, right??? Everything is going on in the
 Documents folder.
 
  Any insights would be greatly appreciated. My 2006 iMac cannot run
 Mountain Lion, so I cannot simply do the upgrade to see what is going on.
 
  Regards,
 
  Bruce Pokras
  Blazing Dawn Software
  www.blazingdawn.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

___
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: Help needed: Shell script stopped working in Mountain Lion!

2012-08-26 Thread Dr. Hawkins
On Sun, Aug 26, 2012 at 2:08 PM, Bruce Pokras bruc...@comcast.net wrote:
 Users of my application who have upgraded to Mountain Lion are left with a 
 folder
full of TIFFs and an error message from my application that it could not find 
any
PDFs to combine into the final single PDF patent file. Does anyone have an 
idea what could be happening?

It looks like Matthias has already given the answer (which is also
useful to me!), but this caught my interest.

What are you using to combine pdf files?  Everything I've looked at so
far would resort to the command line (probably with gs) on macos 
linux, and I don't know yet on WIndows.

I'm dealing with outputting my own cards (which I do by export to
pdf), but I have a couple of external pdf that need to go in, which
I'm currently converting to png, putting on a card, and sending out as
part of the pdf export sequence.



-- 
The Hawkins Law Firm
Richard E. Hawkins, Esq.
(702) 508-8462
hawkinslawf...@gmail.com
3025 S. Maryland Parkway
Suite A
Las Vegas, NV  89109

___
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: Help needed: Shell script stopped working in Mountain Lion!

2012-08-26 Thread Bruce Pokras
Thanks everyone for the responses. Looks like cupsfilter is the way to go. Do I 
need to name a .ppd file, or is that optional? Also, I don't see where I name 
the input filename. I am a HyperCard scripter from way back, so I am dependent 
upon others for stuff like this. So if I have the input file path and the 
desired output file path, what exactly should my get (shell cupsfilter) 
command say?

As for Dr. Hawkins' question about combining the PDF files, I discovered that 
this can be done using a Python script that is a built-in Automator action 
using a command like this:

get shell(python '/System/Library/Automator/Combine PDF 
Pages.action/Contents/Resources/join.py' -o '  thisShort[x]  '   
theAddOn) -- adding pages to the existing file

thisShort is an array of pathnames of _resultant- files to which the 
theAddOn page is added. The previous file [x-1] is deleted once theAddOn page 
is successfully added to the PDF. This command is still working in Mountain 
Lion (thankfully!). I can provide more details if you would like.

Regards,

Bruce


On Aug 26, 2012, at 6:23 PM, Mike Bonner wrote:

 Oh cool! Just read up on cupsfilter and it looks like you're right.
 
 On Sun, Aug 26, 2012 at 4:14 PM, Matthias Rebbe 
 matthias_livecode_150...@m-r-d.de wrote:
 
 Bruce,
 
 if i remember right, but i could be wrong, then convert was just a symlink
 for cupsfilter.
 
 
 https://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man8/cupsfilter.8.html
 
 
 Regards,
 
 Matthias
 
 
 Am 26.08.2012 um 23:08 schrieb Bruce Pokras bruc...@comcast.net:
 
 Hello all!
 
 I develop an application called Patent Grabber that downloads patents
 from various US and international patent authorities. Unlike many other
 authorities that provide patent pages in PDF, the US Patent  Trademark
 Office (USPTO) provides patent pages in TIFF. From Tiger through Lion, the
 following script (which I believe came from a member of this group) has
 worked to convert those TIFF images into PDF pages:
 
 put /System/Library/Printers/Libraries/convert into tConvertApp
 get shell(tConvertApp  -f  quote  tiffFile  quote  -o 
 quote  pdfFile  quote  -j application/pdf 21)
 
 Now under Mountain Lion this script has stopped working. Users of my
 application who have upgraded to Mountain Lion are left with a folder full
 of TIFFs and an error message from my application that it could not find
 any PDFs to combine into the final single PDF patent file. Does anyone have
 an idea what could be happening?
 
 Since foreign patent authorities provide patent pages in PDF, I know
 that the other shell script that Patent Grabber uses (which combines
 multiple PDF pages into a single PDF file) works fine. I think that should
 rule out this being a Mountain Lion security issue as a result of my
 application being unsigned, right??? Everything is going on in the
 Documents folder.
 
 Any insights would be greatly appreciated. My 2006 iMac cannot run
 Mountain Lion, so I cannot simply do the upgrade to see what is going on.
 
 Regards,
 
 Bruce Pokras
 Blazing Dawn Software
 www.blazingdawn.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
 
 ___
 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