This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8336 - Print commands do not work on Mac platform
Summary: Print commands do not work on Mac platform
Status: RESOLVED FIXED
Alias: None
Product: Amaya
Classification: Unclassified
Component: UI (show other bugs)
Version: unspecified
Hardware: Macintosh MacOS X
: P2 major
Target Milestone: ---
Assignee: Vatton
QA Contact: Vatton
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-19 15:19 UTC by Lucinda DeWitt
Modified: 2009-12-03 15:15 UTC (History)
5 users (show)

See Also:


Attachments
Amaya Print test from mac (76.78 KB, image/png)
2009-11-23 16:31 UTC, Lucinda DeWitt
Details

Description Lucinda DeWitt 2009-11-19 15:19:53 UTC
When I choose either "Setup & Print" or "Print . . ." nothing happens (either observable or listed in the Console logs).  I have tried changing settings in the "Setup & Print" dialog, but never see any indication that anything is happening.  The application does not crash.

If Amaya has no intention of supporting Printing on the Mac, those options should be grayed out in the Mac version or a dialog should appear indicating what the print options are for Mac users.

Currently using Amaya 11.3-pre1 (though problem has existed at least back to version 9)
Tested on MacOS X 10.4.11
Comment 1 Vatton 2009-11-23 15:42:54 UTC
(In reply to comment #0)
> When I choose either "Setup & Print" or "Print . . ." nothing happens (either
> observable or listed in the Console logs).  I have tried changing settings in
> the "Setup & Print" dialog, but never see any indication that anything is
> happening.  The application does not crash.
> 
> If Amaya has no intention of supporting Printing on the Mac, those options
> should be grayed out in the Mac version or a dialog should appear indicating
> what the print options are for Mac users.
> 
> Currently using Amaya 11.3-pre1 (though problem has existed at least back to
> version 9)
> Tested on MacOS X 10.4.11
> 

Now the generation of a PostScript file is possible
Comment 2 Lucinda DeWitt 2009-11-23 16:13:55 UTC
Just tried to generate a PS file three times.  
No file is created anywhere on my system.


Using Amaya 11.3-pre1 
Tested on MacOS X 10.4.11 PPC
Comment 3 Lucinda DeWitt 2009-11-23 16:31:12 UTC
Created attachment 783 [details]
Amaya Print test from mac
Comment 4 Lucinda DeWitt 2009-11-23 16:33:07 UTC
The image just attached was described in a comment that disappeared while attaching . . .
The image shows the contents of the folder where the .ps files are supposedly being created.

The Console indicates the following (not sure if relevant):

Nov 23 10:20:58 lucinda-dewitts-power-mac-g4 /Applications/Amaya.app/Contents/MacOS/amaya: CGContextRestoreGState: invalid context
Nov 23 10:20:58 lucinda-dewitts-power-mac-g4 /Applications/Amaya.app/Contents/MacOS/amaya: CGContextRestoreGState: invalid context
Nov 23 10:20:58 lucinda-dewitts-power-mac-g4 /Applications/Amaya.app/Contents/MacOS/amaya: CGContextRestoreGState: invalid context
Nov 23 10:20:58 lucinda-dewitts-power-mac-g4 /Applications/Amaya.app/Contents/MacOS/amaya: CGContextRestoreGState: invalid context
Comment 5 Vatton 2009-11-23 16:56:25 UTC
(In reply to comment #4)
> The image just attached was described in a comment that disappeared while
> attaching . . .
> The image shows the contents of the folder where the .ps files are supposedly
> being created.
> 
> The Console indicates the following (not sure if relevant):
> 
> Nov 23 10:20:58 lucinda-dewitts-power-mac-g4
> /Applications/Amaya.app/Contents/MacOS/amaya: CGContextRestoreGState: invalid
> context
> Nov 23 10:20:58 lucinda-dewitts-power-mac-g4
> /Applications/Amaya.app/Contents/MacOS/amaya: CGContextRestoreGState: invalid
> context
> Nov 23 10:20:58 lucinda-dewitts-power-mac-g4
> /Applications/Amaya.app/Contents/MacOS/amaya: CGContextRestoreGState: invalid
> context
> Nov 23 10:20:58 lucinda-dewitts-power-mac-g4
> /Applications/Amaya.app/Contents/MacOS/amaya: CGContextRestoreGState: invalid
> context
> 

The fix is in the CVS version and will be integrated into the release