Closed GoogleCodeExporter closed 8 years ago
-> Set your UI as you please etc.
Original comment by zaha...@gmail.com
on 13 Mar 2013 at 3:24
This would be difficult to achieve. QMainWindow has a saveState and
restoreState method, but it gives a byte object that describes the state for
all tools at once.
We could perhaps keep track of the sizes of the dock widgets ourselves, but I
fear that it may be quite complicated. For instance, the position of a tool is
not in x, y, but in terms of its relation to other widgets ... I don't think
Qt provides a nice API to control such things...
Original comment by almar.klein@gmail.com
on 13 Mar 2013 at 3:38
The saveState and restoreState could be used as part of session information in
the Project context.
As for the specific proportions - if you keep track of the position of a frame
relative to others etc. than in a situation where a user closes a frame and
changes the dimensions of another frame, when reloading the closed frame it
will adjust to the new proportions - which is excellent. You can then save all
of the proportions in a file and retrieve the relevant ones when opening and
closing frames, and QT should be able to handle it.
Original comment by zaha...@gmail.com
on 13 Mar 2013 at 4:08
This sounds like a task that is very suitable for a contributor to work on :)
If someone can demonstrate a working example, based on a simple QMainWindow and
its dock widgets, I can include it in IEP.
Original comment by almar.klein@gmail.com
on 13 Mar 2013 at 7:49
[deleted comment]
I had a feeling...
Let me finish my CS course, then we'll see where we're heading :-!
Original comment by zaha...@gmail.com
on 13 Mar 2013 at 8:03
As part of migrating our code repositories from Googlecode
to Bitbucket, all IEP issues are now tracked at
https://bitbucket.org/iep-project/iep/issues
To view this issue, use this link (with X replaced by the issue number):
https://bitbucket.org/iep-project/iep/issue/X
Issues on Bitbucket can be created by anyone. Commenting on issues requires
login via Bitbucket, Google, Twitter or Github.
Original comment by almar.klein@gmail.com
on 11 Jun 2013 at 2:40
Original issue reported on code.google.com by
zaha...@gmail.com
on 13 Mar 2013 at 3:10