Issue 117180 - Changed behaviour of XDispatchProvider ".uno:Print" ?
Summary: Changed behaviour of XDispatchProvider ".uno:Print" ?
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: PC Windows NT
: P3 Normal
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2011-03-03 09:00 UTC by parc_de
Modified: 2013-02-24 21:06 UTC (History)
1 user (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description parc_de 2011-03-03 09:00:52 UTC
I think, that the behaviour has changed from 3.2 to 3.3 - before 3.3 the dispatcher call below blocked (I opened a document and by doing a call below I get a printer selection dialog - and could select the printer and print the document) - now the dispatcher call returns at once - even though I have not done anything in the printer selection dialog.

XFrame aFrame = this.aOOoInstance.mxDocument.getCurrentController().getFrame();
        XDispatchHelper aDispatchHelper = (XDispatchHelper) this.aOOoInstance.mxMSFactory.createInstance("");
        aDispatchHelper.executeDispatch((XDispatchProvider) aFrame, ".uno:Print", "", 0, new PropertyValue[0]);
Comment 1 jsc 2011-03-03 09:06:03 UTC
jsc -> cd: i am not sure but maybe it's one for you. 

But anyway i don't think that we have guaranteed compatibility for dispatch commands. Means using dispatch commands is on your own risk.
Comment 2 Oliver-Rainer Wittmann 2012-06-13 12:19:12 UTC
getting rid of value "enhancement" for field "severity".
For enhancement the field "issue type" shall be used.