Bug when working with Shell command
Posted: Sat Jan 31, 2015 7:37 pm
Though I am relatively new at LiveCode, I am pretty confident this is a bug. Nevertheless, I am posting here in the beginners forum because I am a beginner and I could be missing something.
I am experimenting with the Shell command to run another application using the command line (on Mac OS X 10.9.5):
When the button is clicked, the code successfully launches RapidMiner. But ...
After I closed rapidminer and returned to LiveCode, the "answer dialog" (I assume) was displayed in a manner making it impossible to "click OK". It's a little hard to describe. What I saw was a window (looking like a gray "band") stretched across the entire width of my screen bearing no icons, text or buttons. I grabbed the title bar and could move the window, but it appeared to stretch "to infinity and beyond" in each direction. I was unable to launch the message box to "relocate" or "resize" the answer dialog (not that I would know how to do that with the message box). I assume that the answer dialog was "blocking" input until I closed it. I was unable to close what I assume was the answer dialog and had to "force close" LiveCode.
Looks like a bug to me.
I am experimenting with the Shell command to run another application using the command line (on Mac OS X 10.9.5):
Code: Select all
on mouseUp
answer the shell of "java -Xms256m -Xmx2048m -jar /Users/erb/rapidminer/lib/rapidminer.jar"
end mouseUpAfter I closed rapidminer and returned to LiveCode, the "answer dialog" (I assume) was displayed in a manner making it impossible to "click OK". It's a little hard to describe. What I saw was a window (looking like a gray "band") stretched across the entire width of my screen bearing no icons, text or buttons. I grabbed the title bar and could move the window, but it appeared to stretch "to infinity and beyond" in each direction. I was unable to launch the message box to "relocate" or "resize" the answer dialog (not that I would know how to do that with the message box). I assume that the answer dialog was "blocking" input until I closed it. I was unable to close what I assume was the answer dialog and had to "force close" LiveCode.
Looks like a bug to me.
