Issue 72609 - UnoControlModels in UnoDialogs need a Visible property
Summary: UnoControlModels in UnoDialogs need a Visible property
Status: ACCEPTED
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: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-15 09:43 UTC by berend.cornelius
Modified: 2013-02-24 21:07 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description berend.cornelius 2006-12-15 09:43:57 UTC
I should be possible to set and query the visibility of a UnoControl in a
UnoDialog at the model. Currently it is not directly possible ot query the
visibility of a UnoControl. Setting the visibility at a control is possible as
described further down.
bc->cd: As we discussed with mt and fs we therefor would like to have Visible
property at the control that meets the following specification, that I extracted
from the coming Uno-awt documentation

Visible:
The property Visible [of the controlmodel] defines whether a dialog control is
to be appear visible on its assigned dialog-step or not. The effective
Visibility of a control is thus derived from the values of both properties Step
and Visible. For example if the Step property of the controlmodel is not equal
to the Step property of the dialogmodel (that denotes the actual visible dialog
step) the control will not be really visible. In contrast the method setVisible(
[in] boolean Visible ) at the interface [IDL:com.sun.star.awt.XWindow] can be
applied to the control and will set the Visibility of the control regardles the
value of the Step property.
Comment 1 carsten.driesner 2006-12-19 14:26:34 UTC
cd: Accepted.
Comment 2 berend.cornelius 2006-12-21 14:36:25 UTC
bc: As soon as this issue is fixed it should be checked if the visibility of all
controls is set correctly after the creation of the dialog windowpeer. Right now
the windowpeer must be created after all controls have been added to the dialog
container, because otherwise their visibilty is always set to true regardless
which step they are assigned to. This behaviour should be changed along with
this issue.
Comment 3 Martin Hollmichel 2007-11-09 17:28:34 UTC
set target from 2.x to 3.x according to
http://wiki.services.openoffice.org/wiki/Target_3x
Comment 4 Frank Schönheit 2007-11-14 06:01:53 UTC
*** Issue 83611 has been marked as a duplicate of this issue. ***