Peter Kümmel wrote:
Abdelrazak Younes wrote:
Hum, we are talking about floating window geometry right? Why do you
think about floatingGeometry_ instead of normalGeometry and
setFloatingGeometry() instead of initNormalGeometry() ?
floating is also a good description, but 'normal' is the name TT uses for this
behavior
(showNormal, normalGeoemtry), sure we could use our own naming.
I didn't know that. English is not my mother tongue but floating window
is more meaningful to me.
+{
+ normalGeometry_ = g;
+ maxWidth=QApplication::desktop()->width()-20;
+}
+QRect QtView::qtViewGeometry() const
+QRect QtView::getGeometry() const
Yes, that's better.
or even better :
+QRect QtView::geometry() const
There is already QWidget::geometry, so maybe we should switch to
floatingGeometry.
I guess so ;-)
I didn't questioned the if but the necessity of the moveEvent() method,
sorry for the confusion. I mean, if the objective is to save the
geometry on exit do that on the closeEvent. Or am I missing something here?
The problem is that at the closeEvent the size and position of the
NOT maximized window is lost, we must remember it somehow, so we can use
it when saving the session data. It makes no sense to save the size/position
of the maximized window, this was the status before my patch.
When the miximized size and position is saved then clicking on the "normalize"
button of the window has no effect, the patch tries to fix this.
When the floating window is 1. moved, 2.maximized and then 3. closed, we have
no actual position without the moveEvent function, because resize is not called.
I understand, thanks.
Abdel.
