The Print Settings pane in the OSX printer dialog, when called up by OpenPrinterDialog, causes all sorts of problems in the underlying main application. Any time a user goes in and attempts to configure the Epson printer settings... -some- (but not all) of the popup menu selections are somehow causing events to fire and leak into the main application.
The result is: things happen in the main application (menu handlers get executed, so that other commands in the File menu, for instance, are executed for no reason at all) and the user sees the application behaving strangely, when it should be doing nothing at all. Along with that, whatever the user has done to try to configure the printer (switch output resolution) doesn't happen and the popup menu choices in Print Settings "stick", rather than change to new settings. Disabling or removing the menu commands that are being fired up from this prevents weird application behavior underneath, but the popup menu commands themselves in the Print Settings pane don't get executed and appear to "stick"; you can't switch from one printer output resolution to another, for instance. What appears to be happening is this: When the Print Settings pane for the OSX print dialog for the Epson driver is frontmost: somehow; the popup menu in Print Settings for output resolution seems to be getting "overlaid" with the main menu back in the main application. This isn't limited to a single menu in the application. In a real-world situation, switching other popups in the Epson driver, such as Media Settings, will incorrectly cause menu commands in non-File-menu menus to execute back in the main application. We've verified that this happens on multiple OSX 10.4.8 systems at different locations. This one is nasty because there doesn't appear to be a workaround, and it breaks printing functionality for at least one commonly used Epson printer driver. It's seen in 3 different Epson wide format printer drivers, minimum (Epson 4800, 7600, and the new 3800 as well). This appears to be 10.4.8 only; RB2006 (all flavors from at least r3 onward) builds. No problems with RB555; no problems with 10.4.6; most likely 10.4.7 is fine, too, otherwise this would have turned up earlier in the summer. Has anyone else encountered this yet (as in, anyone who has Print capability from their RB applications), and if so, has anyone found a workaround? -- David Miller Senior Software Developer, Digital Color Solutions ColorVision _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
