On Thu, 17 Aug 2000, Allan Rae wrote:
> > 1) As I pointed out, layout isn't handled by kdlgedit. So this
> > doesn't use it. Is this OK ?
>
> Is this the geometry stuff you were referring to for the copyright dialog?
>
Yes. I actually had a mail over the weekend from someone who implied Qt
Designer can generate Qt 1.1 only code, which wasn't at all clear from the
tarball of Qt 2.2.beta. If this is true, then we can switch to using that,
and everyone is happy :)
> [2&3 will have to wait till I have time to read the code and figure out
> what you are talking about...]
>
> > 4) I wasn't sure about using ButtonPolicies as i've not examined that code
> > yet (STL still looks like line noise to me i'm afraid :()
>
> With a vector implementation it should look like a two dimensional array.
> You have to write your own version of ButtonController that works with
> Qt/KDE buttons in the same manner that xforms/ButtonController.h does.
> The STL code used is pretty simple. So just look at what ButtonController
> does and don't worry about the implementation of ButtonPolicies. Just
> worry about which button policy is appropriate for a given dialog.
>
> Also don't feel that you _have_ to use the existing policies. If KDE has
> different ideas about what an applicxation should do with its buttons then
> maybe implement
>
OK, that's good. I think it might be useful anyway, I'll look at this.
>
> Or better yet try using a status variable as defined in
> DialogBase.h. Even better would be to use the appropriate policy from
> button policy. I'm thinking about adding a "list<FL_OBJECT> read_only;"
> to ButtonController so that we can push all the widgets we want disabled
> on a read-only status (or some other status as defined by the policy) into
> the list and then not have to worry about handling de/activation
> separately.
>
> Allan. (ARRae)
>
yes, a button policy seems to be the way to go on this. Note in kde/ I
hide the "OK" button, and make Cancel "Close". This seems a more sensible
presentation to the user ...
thanks Allan !
john
--
"The path you specified contains too many directories. Delete one or more
directories or clear the Include Subdirectories checkbox."
- Microsoft Office