Issue 26782 - Do documentation ANYWHERE on printer name formats!
Summary: Do documentation ANYWHERE on printer name formats!
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: issues@documentation
QA Contact: issues@api
URL: http://api.openoffice.org/docs/common...
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-22 02:34 UTC by halvaughan
Modified: 2013-02-24 21:10 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description halvaughan 2004-03-22 02:34:29 UTC
When working with a Properties object for changing the properties of an
XPrintable object, printer names MUST be bracked like this: <printer> -- this is
not in the documentation.

For example, this does not work:

XPrintable oPrint = (XPrintable) UnoRuntime.queryInterface(XPrintable.class, oDoc);
PropertyValue[] printOpts = new PropertyValue[1];
printOpts[0].Name = "Name";
printOpts[0].Value = "<"+myPrinterString+">";
oPrint.setPrinter(printOpts);

BUT This DOES NOT -- replace the 2nd to last line with:

printOpts[0].Value = myPrinterString;

and the printer is not changed at all.  There is no documentation stating that a
printer name needs to be bracketed (I lost a day troubleshooting this).  The
"Generic Printer" name is not bracketed.  Please add to the documentation that
this bracketing needs to be done in naming printers.

Also reference another example where this is discussed:

http://api.openoffice.org/docs/DevelopersGuide/Text/Text.htm#1+2+3+1+Printer+and+Print+Job+Settings
Comment 1 scarr 2004-04-09 02:16:59 UTC
This should be on the API project as it deals with API documentation.
Comment 2 thackert 2004-11-21 17:10:59 UTC
I have seen that this issue was assigned to OOo-1.1 and that the last entry was
in April. Does this happens also with newer versions of OOo with their new API,
documentation and such? Or could this issue be closed by the the original reporter?
Comment 3 leggewie 2005-02-04 21:29:07 UTC
thackert, there is a huge backlog of issues.  Closing issues just because noone
has yet the time to look at it does not help anyone.  AFAICT this issue is still
valid.
Comment 4 christianjunker 2005-07-08 20:04:04 UTC
I have tested both on 1.1.4 and 2.0 beta and the brackets are not needed, they
are actually wrong! It is like officially documented, no brackets needed.
Comment 5 christianjunker 2005-07-08 20:05:22 UTC
set to invalid.
Comment 6 christianjunker 2005-07-08 20:07:50 UTC
closed.