On Wed, 3 May 2006 12:44:47 +0200 (CEST)
[EMAIL PROTECTED] wrote:
> >> >> Manny forms in Lazarus have a OK and Cancel button an many forms
> >don't > >> show uniform. Ok an Cancel buttons have different size. One
> >time Ok > >> button is on the right on an other form the button is left
> >the Cancel > >> button.
> >> >> It's not a good idea to place OK on all on the right and the cancel
> >> >left > the ok button?
> >> >
> >> > This is common for windows. MacOSX people would expect the other way
> >> > round.
> >> > That's why there is TButtonPanel. It must be improved a little bit,
> >but > > then
> >> > we might use it for many dialogs.
> >>
> >> Mattias,
> >>
> >> I was just about to do some work on the TButtonPanel to finalize it.
> >> (Attaching an OnClick event to a button still does not properly work).
> >You >
> >> mention that it still needs some improvement, can you be more specific?
> >Do >
> >> you have any requests ;) ?
> >
> >Yes.
> >
> >- Bug: TButtonPanel publishes its buttons. Because the buttons are not
> >owned by the form, TWriter writes all properties of each button multiple
> >times to the .lfm. And because of the internal creation order this leads
> >to access violations during loading in some combinations.
>
> The buttons are owned by the TPanel they are on. Do you have another
> suggestion?
Either extend TWriter to keep a list of streamed components, not owned by
the LookupRoot. Or do not publish the buttons itself, but create mapper
TCollectionItems as I suggested below.
>
> >- It needs more types of buttons
> >- It needs custom buttons
>
> I'm not shure it that would be the right way to go. The purpose of the
> buttonpanel initially was to create a container for standard dialogs. It
> is however possible to rename each button as desired.
MessageDlg and QuestionDlg show how to do it. At least it should provide all
TBitBtnKind.
> >- Maybe instead of publishing a fixed list of buttons, better publish a
> >TCollection of panel buttons.
> That could be an option to create a button container that is fully
> customizeable. Perhaps we should consider making this component
> TCustomButtonpanel.
>
> One problem I still have is that when I click on a button in the IDE on
> tbuttonpanel I get focus en I can edit the properties without problems.
It is a bug. Controls not owned by the LoopupRoot are inner parts of a
control, that should not be edited by the user. They should not be
selectable in the designer.
Maybe we can add a ControlState flag, that tells the designer to allow this.
> However the creation of a eventhandler in the sourceeditor by
> doubleclicking in the objectinspector does not work, nor does handomatic
> typing the event name (already existing). The event seems to be readonly.
> Why?
Events are always connected to the LookupRoot. The buttons have as owner the
ButtonPanel, which is not a LookupRoot.
Mattias
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
