Re: Array Properties in a Standalone

On 1/10/17 10:53 PM, Bob Sneidar via use-livecode wrote: It's been my whole understanding of the use of splash stacks that the stack used to create a standalone is read only, and therefore cannot be a stack you set properties of, or make any changes to. I had no idea it became the mainstack in a

Re: Array Properties in a Standalone

First let me say that the 8.1.2 compile time is orders of magnitude improved! WOW what a difference. It was taking me 20 minutes to save as standalone, now it's under a minute. AWESOME! Now on to my tests. Okay I see what is happening. In the IDE the mainstack of a substack is the actual

Re: Array Properties in a Standalone

On 01/10/2017 08:04 PM, Monte Goulding via use-livecode wrote: I can’t give you any solid leads here but I think the idea that custom property sets don’t work in a standalone is a red herring. I’d start by finding the bit of code that sets the custom property set and wrap the whole handler in

Re: Array Properties in a Standalone

> On 11 Jan 2017, at 2:52 pm, Bob Sneidar via use-livecode > wrote: > > In the IDE this works famously. In a compiled application however, the column > updateby in every table I insert or update is empty. The only explanation I > can come up with for this is

Re: Array Properties in a Standalone

I'll try to explain a bit better. I have a splash stack that serves no other purpose than presenting the user with a window with a logo and a message that it is loading the application. It then opens the "actual" mainstack of the application and hides itself. This mainstack is NOT the one that

Re: Array Properties in a Standalone

> On 11 Jan 2017, at 2:24 pm, Bob Sneidar via use-livecode > wrote: > > Ooookaaay. In the IDE I can set a property of the mainstack (not the Splash > Stack mind you that I use to "shell" the application) to an array. When I > retrieve that property and access a

Re: Signing Problems

I managed to get the OSX version of my app signed using Trevor’s code signing stack. Great! But with Appwrapper 3, I got it signed successfully, but then, for some reason that I have yet to find, it no longer access my resource files correctly. The files were available, I could get a list of

Array Properties in a Standalone

Ooookaaay. In the IDE I can set a property of the mainstack (not the Splash Stack mind you that I use to "shell" the application) to an array. When I retrieve that property and access a key of that array, all is well. HOWEVER... when I compile to a standalone, that key is apparently

Array Properties in a Standalone

Ooookaaay. In the IDE I can set a property of the mainstack (not the Splash Stack mind you that I use to "shell" the application) to an array. When I retrieve that property and access a key of that array, all is well. HOWEVER... when I compile to a standalone, that key is apparently

Re: Documentation on Dispatch

I use this ALL the time. sqlYoga uses special arrays for Record Objects, and the elements of one of these arrays can *only* be modified using the sqlrecord_set command. Because of this, I need to pass these record objects by reference to update them correctly. Very handy. Bob S On Jan 10,

Re: Documentation on Dispatch

Since Livecode version 7.0 it’s also possible to pass an array element by reference and that also works with “Dispatch”. Example: on mouseUp Put "27" into tTemp["tKey"] Dispatch "AdjustSetting" with tTemp["tKey"] # Now tTemp["tKey"] = 62 put tTemp["tKey"] end mouseUp on

Re: Documentation on Dispatch

Another feature of “dispatch” that is undocumented is that it can be used with call by reference variables. The variables passed as call by reference can also be arrays, which can come in handy sometimes. Example: on mouseUp Put "27" into tTemp Dispatch "AdjustSetting" with tTemp #

Re: Documentation on Dispatch

Monte Goulding wrote: > Try this: > > on mouseUp > dispatch function "foo" to me with 1,2 > put the result > end mouseUp > > function foo p1, p2 > return p1 + p2 > end foo Yep, it works. So it's not so much wrapping it per se, just calling it directly by adding the "function" specifier to

Re: Documentation on Dispatch

Try this: on mouseUp dispatch function "foo" to me with 1,2 put the result end mouseUp function foo p1, p2 return p1 + p2 end foo ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage

Re: Documentation on Dispatch

Ali Lloyd wrote: > The `dispatch function` form of the dispatch command indeed does not > appear to be documented. What does that syntax look like? This works: on mouseUp dispatch "foo" to me with 1,2 put the result end mouseUp on foo p1, p2 return p1 + p2 end foo ...but this does

Re: Documentation on Dispatch

The `dispatch function` form of the dispatch command indeed does not appear to be documented. On Tue, Jan 10, 2017 at 9:10 PM Richard Gaskin via use-livecode < use-livecode@lists.runrev.com> wrote: > Sannyasin Brahmanathaswami wrote: > > > Sometimes you want to do a "remote" call to a function

Re: Documentation on Dispatch

A perhaps better way is to put all your functions that you want to call "remotely" in a button or a script only stack and when you first open your stack insert the script of into front or back. One thing to keep in mind however is scoping. "this" for example refers to the object which called

Re: Documentation on Dispatch

Sannyasin Brahmanathaswami wrote: > Sometimes you want to do a "remote" call to a function and get data > back. At first this appear no possible > > send | dispatch | do | call > > BUT: FYI you can wrap a function in Dispatch and the value is > returned in the result. > > this is not documented.

Documentation on Dispatch

for the documentarians among us. Sometimes you want to do a "remote" call to a function and get data back. At first this appear no possible send | dispatch | do | call BUT: FYI you can wrap a function in Dispatch and the value is returned in the result. this is not documented.

Re: LC-Magick Collection

Update to LC-Magick #5: Circular (Polar) Image Distortion http://forums.livecode.com/viewtopic.php?p=14#p14 Bernd solved the antialiasing-border-problem with a brilliant technique (using a fillGradient). Needs some more time but it's worth. Thanks BerndN! > Added today #5: Circular

Re: save stack as filename failing most of the time

I tried, but it works fine for me every time in LC8.1.2 (Build 14013) (I no longer have RC3 installed), on MacOS Sierra 10.12.2. This is the test script I used: on mouseUp put"/Users/paulhibbert/Documents/001 Test Folder/paultest.xx.to.Compile.livecode" into tFileName replace "xx" with char

Re: Signing Problems

And I have heard also expensive, which explains why some vendors do not bother. Bob S On Jan 9, 2017, at 19:17 , William Prothero via use-livecode > wrote: Folks: Never mind…. Signing is such a pain.

Re: save stack as filename failing most of the time

livecode has been unable to reproduce the bug. Could someone who was able to make a stack to manifest this please upload? *Comment # 1 on bug 19042 from Panos Merakos

Re: mobile sound: set start point?

Hi Ben, > Am 10.01.2017 um 11:44 schrieb Ben Rubinstein via use-livecode > : > > With a player object, we can get/set the 'currentTime' property to play a > portion of a sound file. > Is there any way to do the same on mobile (specifically, iOS), or are we >

AW: Signing Problems

Hi Bill, I have also experienced signings without error, which actually failed. After signing you should always verify the signing via terminal with: spctl -a -t exec -vv so you don't need to make the way with your server. Tiemo -Ursprüngliche Nachricht- Von: use-livecode

mobile sound: set start point?

With a player object, we can get/set the 'currentTime' property to play a portion of a sound file. Is there any way to do the same on mobile (specifically, iOS), or are we limited to always playing from the start of a clip? TIA, Ben ___