Update for Macintosh and PackageTools
Posted July 7th, 2011 by jjweimer
| Project: | Window Desktops |
| Version: | IGOR.6.01.x-1.3 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | duplicate |
Jump to:
Description
Adam: I'm attaching a ZIP archive with the procedure files as I have modified them to display the panel layout better on a Mac and to interface (almost fully) with PackageTools. I have commented out one portion that is to remove the package -- it did not work as I expected. I think it did not work on my system because I keep ACL_WindowDesktops loaded from Igor Procedures. That may indicate a bug in my PackageTools package that I need to track down. I added an entry level for help file to ACL_WindowDesktops to work with PackageTools#PackageHelp("ACL_WindowDesktops").
I continue to find this package very useful! -- Jeff
| Attachment | Size |
|---|---|
| ACL_WindowDesktops.zip | 17.94 KB |
#1
I've also discovered a strange behavior with Window Desktops and a newer package that I am developing. The fix may require to check that the front window is not the panel and to bring the actual frontmost window forward (DoWindow/F ...) before assigning it to a different desktop. I am not sure why this is happening ... it does not happen if I insert a print topWindowName selectively in the code ... perhaps something I am doing wrong with setting a window hook on my own panel to respond to activate events at that panel.
#2
I'd rather handle the issue with the layout of the panel looking bad on the Macintosh in the original issue at #1030: Button Layouts on MacOS 10.5/Igor 6.10.
For the comment in #1, please create a separate issue and give a recipe to repeat the bug, if you can.
Regarding package tools integration, I don't think I want to do that, since I'd rather not add code to Window Desktops that specifically calls code in another package, even if the call is conditional. Also, I'd rather that we (WM) come up with some kind of package management rather than trying to implement it in procedures. Granted, that may take a while....