Jean-Marc Lasgouttes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
I understand that point but the solution is not to forbid this docking
behavior but to make it hard to dock by default.
"Forbid". You make it sound as if I am trying to censor you creativity :)
The quesiton is not why we should forbid it, it is why we should do it.
You mean "compare keeping your hands on the keyboard with reaching
for the mouse"?
I use mouse gestures a lot on firefox for these cases, but never tried
to use them on a larger scale. This is the best solution I know though.
- have a title bar like a dialog, not this tiny excuse for a handle
?? You have it already.
Face it, an undocked window is not a dialog, but a second class window,
palette-like with a smallish greyish title bar. I don't like them
(which is my prerogative).
On windows the title bar is exactly the same except for the missing icon
on the left. Surely, this too is fixable.
- have an aspect ratio that minimizes mouse movement; there has to be
a reason why all dialogs are not a long vertical strip of controls...
This is fixable.
I am curious to see that, short of designing every dialog twice.
I'd hope that by grouping some controls together the different element
would reposition automatically when the windows is resized. But I did
not manage to find out how to do this. I am not sure this is feasible
though... Andre', would you care to comment or investigate with your
colleagues?
All in all, I think designing the UI with full-screen as first goal is
an error. And designing as panels things like paragraph settings is an
error too. Panels are much more effective (in my view) when they are
carefully chosen.
Yep, your "personal" view ;-)
I know what I write, and being aware of one's own subjectivity is a
good first step.
The right solution is probably to find literature about this kind of
issues. None of us is a professional UI designer, AFAIK.
Sure.
But there is also a code level reason why I want to keep the dialog as a
dock widget for now: Right now, the dialog is only inheriting from a
QWidget, it doesn't know if it is going to be embedded in a QDockWidget
or a QDialog. The result is that the code is much simpler: no button
controller, no slotOK, slotApply, etc. You basically just have to
program in Qt to create a new dialog.
When I've implemented the DialogView container I was talking about, I
will transfer this dialog to that.
Abdel.
