I think this build should fix the issue, but I cannot confirm that myself: rube-mac32-1.5.2-rc1.zip
Could some 10.9 users give it a try before I make a proper update? Thanks!
R.U.B.E bug OS X 10.9 Mavericks
Re: R.U.B.E bug OS X 10.9 Mavericks
Works! Just drop in the same location as R.U.B.E.app and you're good to go.
Re: R.U.B.E bug OS X 10.9 Mavericks
Yep, works perfectly for me too! Thanks for the fix @iforce2d, I look forward to seeing it come through in the next build 
Re: R.U.B.E bug OS X 10.9 Mavericks
Okay, this should be fixed by v1.5.2 which has just been uploaded. Thanks for being patient 
-
therealcos
- Posts: 16
- Joined: Tue Aug 20, 2013 7:30 am
Re: R.U.B.E bug OS X 10.9 Mavericks
I tried everything in this thread and I'm still seeing this issue. I just downloaded v1.5.4 and it's still giving me the same problem - any ideas?
-
therealcos
- Posts: 16
- Joined: Tue Aug 20, 2013 7:30 am
Re: R.U.B.E bug OS X 10.9 Mavericks
Gah, nevermind me - it works!
Re: R.U.B.E bug OS X 10.9 Mavericks
I'm getting this problem in Mac OS 10.13, with R.U.B.E. 1.7.4. Symptoms exactly the same: if launched the normal way, the help file is not found and no actions are registered. Works fine if launched form the command line within the application directory. Is this a regression? It's quite inconvenient.
Re: R.U.B.E bug OS X 10.9 Mavericks
With each new OS release Apple seems to find new ways to break existing programs that were working perfectly well before. I suppose you could call that regression. While Windows and Linux continue to run decades old software without any problems, Apple has a total disregard for basic backward compatibility.
If by 'inconvenient' you mean that you need to open a terminal and type something, I'm pretty sure you could set up a way to just have it clickable from the dock (again, on Windows or Linux this would be pretty trivial but with OSX I have learned to never assume anything will be easy). Perhaps some ideas here might help: https://stackoverflow.com/questions/281 ... -os-x-dock
It's quite likely that if you make a shell script to run a GUI program, the terminal window will hang around the whole time it's running (and closing the terminal window will kill the program) which can be annoying. On Linux you can use 'disown' to avoid this by relinquishing parentage of a background process, for example:
./myprogram.sh &
disown
... now you can close the terminal window and the GUI application will keep running. I have not checked if this works on OSX but 'disown' does seem to exist at least, so it's worth a try.
If by 'inconvenient' you mean that you need to open a terminal and type something, I'm pretty sure you could set up a way to just have it clickable from the dock (again, on Windows or Linux this would be pretty trivial but with OSX I have learned to never assume anything will be easy). Perhaps some ideas here might help: https://stackoverflow.com/questions/281 ... -os-x-dock
It's quite likely that if you make a shell script to run a GUI program, the terminal window will hang around the whole time it's running (and closing the terminal window will kill the program) which can be annoying. On Linux you can use 'disown' to avoid this by relinquishing parentage of a background process, for example:
./myprogram.sh &
disown
... now you can close the terminal window and the GUI application will keep running. I have not checked if this works on OSX but 'disown' does seem to exist at least, so it's worth a try.