Phil Race wrote:
Right you are again. I was looking at the bottom under Parameters - Returns - Throws. You caught me scanning instead of reading the whole thing. However, if after Returns: it had said Object[] or Object array, ... This comes down to a style of how I write documentation and expect it to be written. But then it takes me longer to write doc'n than others and time is money.Unfortunately the API doc'n doesn't say anything about an array, it just says `values'. If the API doc'n used Object[] instead of just Object it would be more clear on this point.I see this in the doc for getSupportedAttributeValues: "Return an array of one or more instances of the attribute category, containing the legal values -- used, for example, by an attribute with a list of enumerated values. The type of the array is an array of the specified attribute category type as returned by its getCategory(Class)" you now owe me two beers.
Yep, I owe you two beer. If I get to a whole case I'll have to send you an AB.
Closure. In a sense a printer is a graphics devices like a display and I wanted to see how complete the Java2D APIs were, especially given what I saw in the documentation. I wasn't exactly planning on using it - although having a virtual space of multiple printers would be cool - just kidding.One more time, are there any ways to get a GraphicsContfiguration for a printer or printerJob?What for? (ie what's interesting that's not better placed in javax.print as an attribute on the service)
You mean you cannot getDeviceConfiguration before you are printing? At this point I'm assuming it is not possible to get a GraphicsConfiguration for a printerJob (i.e., it's Sun proprietary confidential information) :-)Graphics has a getDeviceConfiguration method, but its on the graphics when you are already printing, and what it returns now isn't really very interesting anyway.
Thanks again, Cheers, Eric
-phil.
