To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108951
Issue #|108951
Summary|toolkit: new controls Frame, MultiPage + Page
Component|gsl
Version|DEV300m70
Platform|All
URL|
OS/Version|All
Status|NEW
Status whiteboard|
Keywords|
Resolution|
Issue type|ENHANCEMENT
Priority|P3
Subcomponent|code
Assigned to|npower
Reported by|npower
------- Additional comments from npo...@openoffice.org Thu Feb 4 11:58:34
+0000 2010 -------
Trying to import Userforms sucks, especially when dealing with container
controls
But why is that a problem? firstly use of container controls is very very
comment ( e.g. Frames ) which are mapped to a GroupBox by the filter don't do
any grouping, additionally a GroupBox isn't really a container which means
a) a Frame imported as non Visibile should mean that all containee controls
are also invisible ( but that isn't the case )
b) the filter has to go to huge trouble ( and doesn't do a good job ) at
trying to fake other container aspect of things like
1) grouping for radio buttons
2) position of controls relative to the parent container ( Frame in this
case )
3) tab order
4) doesn't do things like realise that a containee control may completely
or partially visible due to being clipped by the boundry of the parent control
etc. etc. etc. If you add in then trying to support vba api of said imported
Userforms then the pain even increases more, but... it gets worse because
a) Userforms can ( and do ) support multiple levels of containment e.g.
Userform->Frame1->Frame2...
b) there are *other* containment controls like MultiPage ( and the associated
Pages )
so, I have created some initial implementations for these controls, the
intention is to initially just use these controls for the Userform import only (
but the plan is to of course make them generally available in the future )
I hope we can integrate the cws with these controls implemented as is ( well of
course I hope you both ( Frank & Carsten ) ) will help me stabilise the code
that by cleaning up what's there already and at least ensuring the existing
code's behaviour is unaffected by these changes and behaves as before )
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@gsl.openoffice.org
For additional commands, e-mail: issues-h...@gsl.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
