You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 9, 2017. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 9, 2017. It is now read-only.
Sort of. Maybe. Over at the Shoes 3.2 issues there is shoes/shoes3#26 which shows the window events and their problems. Not mentioned there is that if you call exit() none of the gui events fire.
Shoes 3.2 is a lot more refined than 3.1 (the repo you reported this bug to ) and it works better than it ever did. Shoes 4 is the java/swt version that isn't completely nailed down.
To close/kill a Ruby spawned process (not really a Shoes process/window) is highly platform specific. I suggest you file a new bug report at https://github.com/Shoes3/shoes3 with some additional details (like the platform you are using) or if your running Shoes4 then the issue tracker is https://github.com/shoes/shoes4
Activity
ccoupe commentedon Apr 8, 2015
Sort of. Maybe. Over at the Shoes 3.2 issues there is shoes/shoes3#26 which shows the window events and their problems. Not mentioned there is that if you call exit() none of the gui events fire.
AJFaraday commentedon Apr 9, 2015
So what I'm getting from that is that I should probably try the newer, possibly less finished version of Shoes?
(Incidentally, my app is launching another app, and I need to close it to avoid zombie processes (so UI actions aren't really the problem)
ccoupe commentedon Apr 9, 2015
Shoes 3.2 is a lot more refined than 3.1 (the repo you reported this bug to ) and it works better than it ever did. Shoes 4 is the java/swt version that isn't completely nailed down.
To close/kill a Ruby spawned process (not really a Shoes process/window) is highly platform specific. I suggest you file a new bug report at https://github.com/Shoes3/shoes3 with some additional details (like the platform you are using) or if your running Shoes4 then the issue tracker is https://github.com/shoes/shoes4