OK, that did the trick.trevor wrote:It's the mac part that's causing it. Just add "run" to the end of the command line you put in your shell script.
Odd though, shouldn't it run when you double click the jar?
Moderators: dorpond, trevor, Azhrei, Craig
OK, that did the trick.trevor wrote:It's the mac part that's causing it. Just add "run" to the end of the command line you put in your shell script.
Actually that was the change that made the dialog show up. People that were unfamiliar with the difference between a bat file and a jar file were double clicking the jar file, which runs at default memory, and then they get all sorts of weird errors and connection problems because they run out of memory. So I made the default launch of the jar file tell the user to use one of the supplied scripts. I could put in some of the shell scripts for linux/OSXmosat wrote: Odd though, shouldn't it run when you double click the jar?
That would be good but I couldn't tell you how to do it, my script is dependent on the files location, but I'm not very code savy.trevor wrote:I could put in some of the shell scripts for linux/OSX
True, and I've done this before for a different app. I might take a look at throwing this together until we get it into an automated buildmosat wrote: The better solution we have is a separate download for Macs. We use the Jar Bundler to create a Mac app package which contains all the files as well as the additional memory bump and a nice big OSX icon. It makes it look and feel more like a Mac program.