Flish-flash MacOS standalone problem

My recent release of Devawriter Pro (2.6.2 refactor 3) was built as a "fat binary" for Macintosh and bundled it off to the Monks in Hawaii who were, justifiably, disgruntled, because the thing refused to quit, and on attempting to do flashed about on the screen and had to be 'Force Quit' to get

Re: Quitting a Standalone Problem

Hi , Had no problem using "quit" in all versions , How do you intent to initiate the quit ? Regards Camm - Original Message - From: "Charles Szasz" To: use-livecode@lists.runrev.com Sent: Thursday, 27 March, 2014 2:55:35 AM Subject: Quitting a Standalone Problem

Re: Quitting a Standalone Problem

Hi Charles, No, I don't think the "bug" was solved. The bug you're referring ro is probably that the engine stays running in memory after closing all stacks. This is my standard script: on quitThisApp lock messages -- MySql -- put revOpenDatabases() into myDatabases -- repeat fo

Quitting a Standalone Problem

Is there a standard script for quitting windows standalones? I have run into this problem on Windows XP, Windows 7 and 8. The Rev Archives indicate that there was a bug In quitting standalones. Was this bug resolved in LC 5.5.5? A link to a solution in the archives is no longer active. Sent

Re: Standalone problem

Thanks Jacque, as usual you have the right answer! Might be useful to document everything I tried and the results. I did try setting up the folder structure outlined in the newsletter article since it says "You only need the *Runtime* hierarchy for building Standalones containing your externals."

Re: Standalone problem

On 5/25/12 7:20 PM, Peter Haworth wrote: Jacque, Bit late on this but I've just successfully built an external( whooppee!) and am now left with the task of installing it in the correct place. Congrats. :) I know it was a difficult trek. I've never had to deal with any of that, and I don't thin

Re: Standalone problem

Jacque, Bit late on this but I've just successfully built an external( whooppee!) and am now left with the task of installing it in the correct place. I understand your explanation in this thread. I guess my question relates to the newsletter article that explains how to make an external and use

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

Re: Standalone problem

Hi Craig, please check my new answer in the forum! Best Klaus -- Klaus Major http://www.major-k.de kl...@major.on-rev.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your su

Re: Standalone problem

On 5/13/12 11:50 PM, J. Landman Gay wrote: You can only load externals in a preOpenStack handler, I had a thinko. It's "startup" I believe. They may both work, it's been a while so I'd need to check. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software

Re: Standalone problem

On 5/13/12 11:22 PM, dunb...@aol.com wrote: Jacque. If I do not include a full pathname to the external in the stack inspector, neither the IDE stack nor the standalone will work.The external is not seen unless I go through the process form the "external references" pane, navigating to the exter

Re: Standalone problem

Jacque. Klaus had said that there is a bug in the standalone builder, that non-LC externals are not loaded into the package. He is right. But, I wrote this to Klaus in the forum: Klaus. You are right, the bundle is not included in the package contents. However: 1- Neither is it included in

Re: Standalone problem

On Sat, May 12, 2012 at 1:43 AM, wrote: > This may be too specialized a problem for anyone to know what is going on. > The production machines are running OSX 10.7, though the developing machine > is running OSX 10.6. All are MacBook Air. > > The Service USB Plus Driver software is installed on a

Re: Standalone problem

On 5/11/12 12:43 PM, dunb...@aol.com wrote: But when I loaded the app onto another Mac, although all screen functionality works perfectly, the control signals are not implemented. It sounds like the app can't find the external. Do you see it in the standalone bundle? It should be next to the

Standalone problem

I have made a custom application to control a lighting system. I am using a hardware interface known as a "Service USB Plus", from Bonig and Kallenbach. Works fine in the IDE, sending data via USB to the interface, which does its thing. The working stack references an external framework bundl

Re: Standalone problem

On 3/10/11 11:18 AM, edward cawley wrote: Thank you much Jacque, I'm almost there. I made the changes you suggested and I have one remaining problem. If I run it off the shared disk in VM Fusion it works fine, but if I move the app and associated files to the C drive on the students laptops, or

Re: Standalone problem

Sounds like a local system problem. Try refreshing the folder view. I have copied files before and the view for whatever reason did not refresh properly, even after I closed and reopened it. The only other thing that could affect it is special permissions on the files themselves. If you know h

Re: Standalone problem

17 AM, use-livecode-requ...@lists.runrev.com wrote: > > > Message: 11 > Date: Tue, 08 Mar 2011 21:53:14 -0600 > From: "J. Landman Gay" > To: How to use LiveCode > Subject: Re: Standalone problem > Message-ID: <4d76f9aa.50...@hyperactivesw.com> > Cont

Re: Standalone problem

On 3/8/11 9:11 PM, edward cawley wrote: I modified Francis code as follows: put the platform into GVHoldPlatform if GVHoldPlatform = "MacOS" then put "misippfiles/" into GVStackPath -- No leading drive on the Mac. end if if GVHoldPlatform = "Win32" then -- Syste

Re: Standalone problem

edward- Tuesday, March 8, 2011, 7:11:05 PM, you wrote: > put item 1 of specialfolderpath("system") & > "/misippfiles/"into GVStackPath-- Get Stack Path with Disk ID. > replace "WINDOWS/" with empty in GVStackPath -- Remove Windows > Folder Name. What's your itemdelimiter set

Re: Standalone problem

Forgot to change the Subject line,try again. Still having trouble with a standalone to Windows. I know what's wrong but I'm not sure how to debug it. The program loads, the substacks work in the menubar and the navigation buttons all work, and some of the images grouped over the buttons also sh