Re: Apple Deprecated "UIApplicationExitsOnSuspend"

2020-03-10 Thread Sannyasin Brahmanathaswami via use-livecode 
Ha I should have waited for you... I edited the settings.plist in all 

~/Applications/LiveCode Business 9.6.0 (dp 2).app/Contents/Tools/Runtime/iOS # 
a six settings files

And used Ralph method

Edit the script of stack revSaveAsIosStandalone

And delete 1709

It worked. Transporter says "DELIVERED ON MAR 10...

YAY!   I try your method next time 

BR


On 3/10/20, 1:15 PM, "use-livecode on behalf of matthias rebbe via 
use-livecode"  wrote:



> Am 10.03.2020 um 23:10 schrieb Sannyasin Brahmanathaswami via 
use-livecode :
> 
>  If you can edit the pList on in standalone, we get another error on 
attempt thru Transporter:


BR,

You cannot edit  the info.plist file directly in your standalone app 
bundle. 

You have to copy that file to the outside of the app bundle, for example to 
the desktop.
Then edit that file on the desktop  and save it.
Then go to Standalone Settings -> Copy Files and add that file (the one on 
the desktop).
Now create your app again. The new standalone will now contain your 
modified info.plist file and the error should not come up when uploading to 
Apple.

Regards,

Matthias



___
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: Apple Deprecated "UIApplicationExitsOnSuspend"

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



> Am 10.03.2020 um 23:10 schrieb Sannyasin Brahmanathaswami via use-livecode 
> :
> 
>  If you can edit the pList on in standalone, we get another error on attempt 
> thru Transporter:


BR,

You cannot edit  the info.plist file directly in your standalone app bundle. 

You have to copy that file to the outside of the app bundle, for example to the 
desktop.
Then edit that file on the desktop  and save it.
Then go to Standalone Settings -> Copy Files and add that file (the one on the 
desktop).
Now create your app again. The new standalone will now contain your modified 
info.plist file and the error should not come up when uploading to Apple.

Regards,

Matthias



___
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: Apple Deprecated "UIApplicationExitsOnSuspend"

2020-03-10 Thread Sannyasin Brahmanathaswami via use-livecode 


   Apple is making it worse.

As March 10, the Transporter/App Store (it seems) will 

a) verify to app (I am on a new Mac with a fresh set of certs and 
provisioning profiles)
b) then, accept delivery of the app 
c) then respond with :"DELIVERRY FAILED ON MAR 10, 2020, AT 11:48 AM".   1 
Issue
d). ERROR ITMS-90339: "This bundle is invalid. The Info.plist contains an 
invalid key 'UIApplicationExitsOnSuspend' in bundle SivaSiva [SivaSiva.app]"

Usually after an hour or so, the build would appear, despite the error and 
you could go to TestFlight. Now after 3 hours, the build will not appear.

AND
 
If you can edit the pList on in standalone, we get another error on attempt 
thru Transporter:

ERROR ITMS-90035: "Invalid Signature. Invalid Info.plist (plist or 
signature have been modified). The file at path [SivaSiva.app/SivaSiva] is not 
properly signed. Make sure you have signed your application with a distribution 
certificate, not an ad hoc certificate or a development certificate. Verify 
that the code signing settings in Xcode are correct at the target level (which 
override any values at the project level). Additionally, make sure the bundle 
you are uploading was built using a Release target in Xcode, not a Simulator 
target. If you are certain your code signing settings are correct, choose 
"Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild 
your release target. For more information, please consult 
https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html;

I guess I have to edit the .plist in the 9.6.dp2 build resources...

Another day lost to Apple


On 6/12/19, 11:31 AM, "Sannyasin Brahmanathaswami"  wrote:

Yes, I tried to re-upload after deleted in the key (without checking 
iTunes first) and it turns out the first app was accepted..., "redundant 
build'' on the 2nd attempt. I went into iTunesConnect and and the app is now in 
for review by the Lords of Apple.

Agreed. We need to find out what "gives" with this key being deleted.

Maybe we well get a "resume" message from  iOS to the LC in the 
engine... that would be interesting.

BR


On 6/12/19, 8:20 AM, "Ralph DiMola"  wrote:

Apparently ALL apps will NOT "exit on suspend" in iOS 12+. The real
question is if we eliminate this key too soon then what will 
happened to pre
iOS 12 installs? I think for now we should keep this key and live 
with the
warnings.
On 6/12/19, 8:20 AM, "Ralph DiMola"  wrote:

I had this problem last week. I have a ticket out but am unable to 
work on
it because our office is moving and we are in shambles. This is 
just a
warning and your .app will be processed and approved for submission 
for app
review. Apparently ALL apps will NOT "exit on suspend" in iOS 12+. 
The real
question is if we eliminate this key too soon then what will 
happened to pre
iOS 12 installs? I think for now we should keep this key and live 
with the
warnings.





___
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: Stacks and Custom properties

2020-03-10 Thread Richmond via use-livecode 
I am only using a single custom property in my *Devawriter Pro* for 
end-users to set the thing to the
left, right or centre of their screen. This is not something that needs 
to persist between user sessions.


On 10.03.20 16:52, Bob Sneidar via use-livecode wrote:

The downside to doing this is that you cannot have your properties persist 
between sessions unless you can save the stack containing the properties. A 
mainstack in a standalone cannot be saved, and other stacks may have issues 
saving if they are in a sandboxed or secured location.

If you are using this just for runtime variables, that would work but it begs 
the question, why? Variables are easier to reference in your code.

Bob S



On Mar 10, 2020, at 03:38 , Kaveh Bazargan via use-livecode 
 wrote:

Absolutely. I keep most of my variables in stack custom properties.


___
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: Revisiting old bones

2020-03-10 Thread Bob Sneidar via use-livecode 
 Have to eat crow. Another function that set the rect of the stack based 
on the objects it contained was the culprit. 

Bob S


> On Mar 10, 2020, at 08:49 , Bob Sneidar via use-livecode 
>  wrote:
> 
> Hi all. Forgive me for dredging up an old issue again, but this really is a 
> bug. 
> 
> When I close a stack I get the loc of the stack and save it in a custom 
> property. When I open the stack I get that property (I checked that it is 
> identical to what I saved it as) then set the loc of the stack to that. It 
> ends up 11 pixels HIGHER than it was when I saved it!! I check the loc of the 
> stack after it opens that's how I know!!!
> 
> If I set the loc of a stack, and what ends up in the property is SOMETHING 
> OTHER THAN WHAT I TOLD IT TO BE, isn't that a bug, Mac Menu Bars 
> notwithstanding???
> 
> Sorry for sounding animated but this really "bugs" me. 
> 
> Bob S


___
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

Revisiting old bones

2020-03-10 Thread Bob Sneidar via use-livecode 
Hi all. Forgive me for dredging up an old issue again, but this really is a 
bug. 

When I close a stack I get the loc of the stack and save it in a custom 
property. When I open the stack I get that property (I checked that it is 
identical to what I saved it as) then set the loc of the stack to that. It ends 
up 11 pixels HIGHER than it was when I saved it!! I check the loc of the stack 
after it opens that's how I know!!!

If I set the loc of a stack, and what ends up in the property is SOMETHING 
OTHER THAN WHAT I TOLD IT TO BE, isn't that a bug, Mac Menu Bars 
notwithstanding???

Sorry for sounding animated but this really "bugs" me. 

Bob S


___
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: Stacks and Custom properties

2020-03-10 Thread Kaveh Bazargan via use-livecode 
Bob, good point. In my case I am using several standalone stacks, so when
the standalone opens, it reads data from a remote location (database
or Google Sheets) and saves them as custom variables. In addition there are
variables that are created throughout a session that are saved in a similar
way. Then these values are available to all stacks throughout the session.
Glad to hear of any thoughts on this.

On Tue, 10 Mar 2020 at 14:54, Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:

> The downside to doing this is that you cannot have your properties persist
> between sessions unless you can save the stack containing the properties. A
> mainstack in a standalone cannot be saved, and other stacks may have issues
> saving if they are in a sandboxed or secured location.
>
> If you are using this just for runtime variables, that would work but it
> begs the question, why? Variables are easier to reference in your code.
>
> Bob S
>
>
> > On Mar 10, 2020, at 03:38 , Kaveh Bazargan via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > Absolutely. I keep most of my variables in stack custom properties.
>
>
> ___
> 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
>


-- 
Kaveh Bazargan PhD
Director
River Valley Technologies  • Twitter
 • LinkedIn

___
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: Stacks and Custom properties

2020-03-10 Thread Bob Sneidar via use-livecode 
The downside to doing this is that you cannot have your properties persist 
between sessions unless you can save the stack containing the properties. A 
mainstack in a standalone cannot be saved, and other stacks may have issues 
saving if they are in a sandboxed or secured location. 

If you are using this just for runtime variables, that would work but it begs 
the question, why? Variables are easier to reference in your code. 

Bob S


> On Mar 10, 2020, at 03:38 , Kaveh Bazargan via use-livecode 
>  wrote:
> 
> Absolutely. I keep most of my variables in stack custom properties.


___
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: Stacks and Custom properties

2020-03-10 Thread dunbarx--- via use-livecode 
Sure. Any object that has an inspector, and that means everything, can hold 
custom properties. Open the stack inspector and check it out.
The trick is to know where to place these things. It depends on what is going 
to need them. In a sense, you might think they ought to fall into some sort of 
"message hierarchy", but since they are always explicitly referenced, this is 
not strictly true. You generally place them according you your own sense of 
structure.
Craig


-Original Message-
From: Kaveh Bazargan via use-livecode 
To: How to use LiveCode 
Cc: Kaveh Bazargan 
Sent: Tue, Mar 10, 2020 6:39 am
Subject: Re: Stacks and Custom properties

Absolutely. I keep most of my variables in stack custom properties.

On Tue, 10 Mar 2020 at 10:36, Richmond via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Can a stack have custom properties?
>
> Richmond.
>
> ___
> 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
>


-- 
Kaveh Bazargan PhD
Director
River Valley Technologies  • Twitter
 • LinkedIn

___
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: Stacks and Custom properties

2020-03-10 Thread Kaveh Bazargan via use-livecode 
Absolutely. I keep most of my variables in stack custom properties.

On Tue, 10 Mar 2020 at 10:36, Richmond via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Can a stack have custom properties?
>
> Richmond.
>
> ___
> 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
>


-- 
Kaveh Bazargan PhD
Director
River Valley Technologies  • Twitter
 • LinkedIn

___
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

Stacks and Custom properties

2020-03-10 Thread Richmond via use-livecode 

Can a stack have custom properties?

Richmond.

___
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: Pinch-Zoom gesture on native textfield. How to?

2020-03-10 Thread William de Smet via use-livecode 
Thanks!

I tested the code on a normal/standard field and it kinda works.
I changed the multitouch-pinch code form image to fld and added a  'set
textSize ...'.
However it doesn't work as expected. The field is changing faster and
bigger then the text inside the field.

Then I found this script on the forum:
https://forums.livecode.com/viewtopic.php?f=53=13435=64556=pinch+zoom+text+field=bc8d11d77d2ab8de722b07bc4863fb09#p64556
Text is resizing but not smooth.


Greetings,

William




Op ma 9 mrt. 2020 om 18:58 schreef hh via use-livecode <
use-livecode@lists.runrev.com>:

>
> http://lessons.livecode.com/m/4069/l/29112-how-do-i-use-native-text-controls-on-mobile
>
> http://lessons.livecode.com/m/4069/l/11509-how-do-i-implement-a-multi-touch-pinch-motion
> ___
> 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