Unsanity's Windowshade X Minimize-In-Place not wroking
Hello,
TenFourFox is not correctly minimizing in place with Unsanity's Windowshade X. A minimized-in-place window will be created behind the original window which will not minimize. If I close the still open window it disappears, then after a few seconds the minimized-in-place window behind it will disappear as well. If I try to re-open it before it disappears the TenFourFox will be all black and then disappear. The attached images will show you more of what happens.
I'm using Unsanity's Windowshade X on my G5 Quad (10.5.8). I've tried different combinations of removing other Windowshade X features but the only one that does not work correctly is the minimize-in-place feature.
I can only imagine the miniscule amount of users still using this archaic (and no longer supported) software. If there is no interest in finding a solution I would understand. On the other hand if anyone would like to troubleshoot this let me know. Unsanity does not exist anymore, I think their software is now considered abandon-ware if anyone wants to install it and try to troubleshoot this. TenFourFox is really the only program allowing me to do anything online anymore, and I love my G5. 11 years and still going strong.
I think the issue may be with how TenFourFox handles minimize commands from Windowshade X. Any suggestions/ solutions would be greatly appreciates. Thanks for reading.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Cameron Kaiser on 16 May, 2016 12:36 AM
Although I sympathise, since OS X really doesn't have anything like the OS 9 windowshading feature, I've never supported haxies even when they were new and even when Unsanity was still maintaining them. In general, they work by monkeypatching components of the OS, and I find the approach fraught with peril and likely to introduce unusual bugs. I don't approve of the approach Unsanity took to implement them even though I salute their creativity.
In this case, the bug is because we actually use an OpenGL context for the window (this is Mozilla's code, not mine) and Windowshade X doesn't know how to cope with that. I don't have a solution for you, unfortunately.
2 Posted by lightningstat on 16 May, 2016 02:11 AM
Ok no problem.
Thanks.
Cameron Kaiser closed this discussion on 20 May, 2016 04:16 PM.