LiveCode Forums.

I am trying to make a stand alone application and using the 'splash' screen substack method as documented by Sarah Reichelt in the revJournal article of 5 May 2005. Here are the settings that I am using for the standalone:
General:
'Search for required inclusions when saving...' is checked
'Remove all profiles on objects' is checked
Default build folder to desktop
Stacks:
'Move substacks into individual stackfiles' is checked
'Set destroyStack property to true' is checked (but I have tried it both ways)
OS X:
'Mac OS X (Universal)' is checked (but I have also tried 'Mac OS X (Intel only)')
'Enter the information and have Revolution write the PLIST file for you' is checked.

Then I take 'Save as standalone application' and produce a folder on my desktop which contains 'Portfolio Manager.app'.
I get the a message that says everything was successful.

When I run the application starts and I can see a generic icon flash on the dock and then the application crashes. I get choices for 'Ignore', 'Report' and 'Relaunch'. The only choice that produces anything is the one for 'Report' but that doesn't make much sense to me. At this point I have not sent anything to Apple because I suspect I have done something wrong not them.

I can examine the package contents of the application and see a lot of stuff that looks familiar and a lot that doesn't.

If I go through the whole process and produce and application for Windows I get an application that does run but not as it should. Just one example would be that a 'click' on a line of a DataGrid does not select the line.

Any suggestions for the Mac standalone? That is the one I really want at this point.

Regards,
Larry

Hi Larry,

Which version of Revolution do you use? If you use 4.5, how large is your standalone (in MB)

Can you include the following in a startUp handler in the stack script of your splash stack:
This will tell you whether the engine starts up to the point where it starts executing scripts, which in turn tells you whether the problem may be in your own stack or in the RunRev engine.

Do you have any objects on in the splash stack, e.g. a GIF image or a background?

Why do you save substacks as individual files? What if you don't?

Best,

Mark

Hi Mark,

To answer your questions:
I am using REV Enterprise 4.5.0-dp-2.
My stack as a .rev is 1.1 MB and the standalone .app is 7 MB.

I included your script in then stack script and the recompiled the standalone. When I ran it it crashed in the usual way without leaving a 'time' file on the desktop. Just to make sure I was doing everything OK I went back to the IDE and manually ran the startup script to see the file that was made to verify that I hadn't missed something. Does this indicate engine?

My splash screen has only a field with a small amount of text and a 'continue' button.

You last question has me a bit confused. After reading that revJournal article I thought that I had to save the files individually if I was making a standalone for the Mac. Do I have other options? Her article mentions 'template stacks', 'preference files' and 'data files' but claims the 'splash' method is easiest.

Larry

Hi Larry,

One way or another, the splash stack needs to be able to find your own stacks. The easiest way is to build a standalone of your splash stack and put your own stack in the same folder as the executable (on Mac, this is inside the application package). The splash stack needs at least the following line:

go stack "name of your stack.rev"

There is no reason to save substacks as separate files.

Best,

Mark

Mark,

Is it possible that the fact that my splash (or main stack) has a menu could be causing the problem? As you are well aware, I have had some problems there too.

Regards,
Larry

Hi larry,

A menubar shouldn't cause problems by itself.

Sorry, I'm completely unaware of "problems there too"

Best,

Mark

Mark,

I made a test version from my set of stacks where I kept the splash stack and deleted all but two of the substacks. The substacks I kept were the one that is opened when you click the continue button on the splash/main stack and the other is the stack that contains all the DataGrid informatiion. I made a standalone of that and it crashes without shoeing the time stamp.

I'm not sure where to go from here.

Larry

PS I just went back to the test stack to actually see how it ran with most of its parts missing only to discover that the stacks I thought I had deleted are still there. Does that sound possible. This is getting frustrating.

lohill wrote:I am using REV Enterprise 4.5.0-dp-2.

Larry, I seem to remember there is a bug in 4.5.0-dp2 that crashes standalones for the Mac. If you are on the improve-list there was a link to a patch.
Try to build with either 4.0 or 4.5 dp-1
regards
Bernd

Hi Bernd,

I was thinking of that patch, but since Larry reports a standalone size of only 7 MB, it seems that he has got the new (patched) version already. The unpatched version should be over 30MB.

Best,

Mark

Mark wrote:I was thinking of that patch, but since Larry reports a standalone size of only 7 MB, it seems that he has got the new (patched) version already. The unpatched version should be over 30MB.

OK, I did not apply the patch and did not build standalones.
It might still be worth trying a non-beta version, e.g. 4.0
regards
Bernd

Bernd said:

Larry, I seem to remember there is a bug in 4.5.0-dp2 that crashes standalones for the Mac. If you are on the improve-list there was a link to a patch.
Try to build with either 4.0 or 4.5 dp-1

Thanks Bernd - you saved my sanity. I went back to my REV applications and found one with a folder that said 4.5.0-dp-1. That is the version I am now using. In the About menu however it says Build 1000 and 4.5.0 with no reference to dp=1.

It does let me make a standalone for my Mac that runs. I'm not out of the woods yet though because like the Windows standalone that I was able to make with 4.5.0-dp-2, the stand alone for my Mac does not respond to a click in a DataGrid. Unfortunately that makes it a non-starter for me.

How does one get notified about patches? When I received notification about dp=2 I just installed it and started using it. It is a bit disconcerting to think that I was 'beta' testing it.

Regards,
Larry

Larry,
glad it helped you.
Since you have an enterprise license you are automatically enrolled in the beta program of Rev. 4.5 is still beta, the latest release version is 4.0. As an enterprise license holder you can subscribe to the improve-list. That is the closed list where the beta versions are discussed since they are not discussed publicly.
With your license you should have gotten an invitation to join the improve-list. If you don't have it anymore just write to support.
regards
Bernd

Thanks for this information Bernd. Since I am still a bit of a novice at this, I think it would be better if I stuck with version 4.0 until I get better. Besides, if I bring up issues I'm seeing on this public forum for what amounts to Beta software it is probably not such a good idea.
I'll let you know if I see any of these problems with 4.0.

Regards,
Larry

Bernd and Mark,

This is very discouraging. I went back to REV Enterprise version 4.0.0 build 950 (my earliest version) and compiled my application as a standalone again. I have something that runs but it is not anything like it would run in the IDE. The most glaring thing for me is that the DataGrids act as though they can't get focus. They do not respond to either a click or a double click. They do not respond to a column heading sort either. My menu items that do things like add or delete rows do not work either. These are all things that have worked in the past while I was in the IDE of 4.5.

I will stay in the 4.0 IDE for now and check everything over there before I try another standalone. What are other people doing that have DataGrids in standalone applications?

Larry

Today I have a clear 'Catch 22'. Using Rev Enterprise 4.0.0 and changing the settings for making the standalone version of my application in the Stacks option by un-checking the box that says 'Move substacks into individual stackfiles', I get a standalone version where the DataGrids seem to work just fine. Unfortunately, if I can believe that revJorrnal article mentioned above (and my own observations) I will not be able to make any changes in my stacks because they won't be saved.

I want to be able to use DataGrids AND save changes so again I ask what are others doing for their Macintosh projects?

Larry