Re: Standalone problem (solved?)

Hi Guglielmo, Got Lion installed today and tried your test app. It behaved the same as with Snow Leopard: 1. Started the app. 2. Clicked the Test MAS button 3. The app quit 3. Got request to log in to Apple Store (I did, using my test account) 4. The app didn't restart. Pete lcSQL Software

Re: Standalone problem (solved?)

OK, understand it now and yes, the behavior was as you outlined. I'm downloading Lion now so should be able to test your app with Lion tomorrow. Pete lcSQL Software On Tue, May 22, 2012 at 3:47 PM, Guglielmo Braguglia wrote: > Hi Pete, > thanks for the report ... > > S

Re: Standalone problem (solved?)

Hi Pete, thanks for the report ... So, normally : 1. you installed the App, 2. you started the App, 3. you pushed the 'Test MAS' button, 4. The App closed and the App Store mask appeared, asking you sign-in (/after few seconds/) At this point, because the App is just a test and it's NOT physic

Re: Standalone problem (solved?)

Hi Guglielmo, Just tested all this. I think it works fine. What is the expected behavior once I've donwloaded a test receipt file? On my computer, the test program just quit. Pete lcSQL Software On Tue, May 22, 2012 at 10:29 AM, Guglielmo Braguglia < guglie...@braguglia

Re: Standalone problem (solved?)

Thanks for this Guglielmo, that's great. I'm still on Snow Leoprad at this point but plan on upgrading to Lion soon, will probably download it overnight tonight. Pete lcSQL Software On Tue, May 22, 2012 at 11:51 AM, Guglielmo Braguglia < guglie...@braguglia.ch> wrote: >

Re: Standalone problem (solved?)

Ah Pete, I forgot ... ... I'm still on SnowLeopard so, all my test are on SnowLeopard using LiveCode 5.0.2 (... /which is not important for the Receipt Validation/), but, because in the test that I linked to you, I have tried to use the Sanboxing structure ... please, if you have a Lion system

Re: Standalone problem (solved?)

Hi Pete, just following your suggestion I bought Receigen and I have spent few days writing an External to use the generated C code :-) Next I wrote a little test App that you can download from there (it's a pkg) : http://www.phoenixsea.ch/downloads/test.pkg ... install, run it and push the b

Re: Standalone problem (solved?)

This is all quite timely for me as I just started, reluctantly, to try to figure out how to write an external. It's discouraging to hear that, even if I get through figuring out how to make an external from the incomplete, out of date lessons on how to do it, there are various other hurdles to ove

Re: Standalone problem (solved?)

On 5/22/12 8:45 AM, dunb...@aol.com wrote: It seems the external must be explicitly referenced, as verified by the authors, and not, in their words, "relatively" referenced. That might be true when calling the external from a script but I can't see how it would apply to how LiveCode recognize

Re: Standalone problem (solved?)

dunbarx wrote: > It is academic to me why this must be, especially since I thought I > had learned something new and important in that one must load third > party externals into the contents folder of a standalone package by > hand. In my case, doing this had no effect at all. I assume that this

Re: Standalone problem (solved?)

Jacques and Klaus... Thanks to both of you. My standalone problem is solved, sort of. It was always the pathname to the external. I had thought so, and mentioned it as a likely culprit in my initial post. It seems the external must be explicitly referenced, as verified by the authors, and