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 "DELIVER
> 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 fil
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
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 t
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
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 t
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.
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 u
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
"
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
>
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
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
12 matches
Mail list logo
