ralsina / marave

Automatically exported from code.google.com/p/marave
GNU General Public License v2.0
0 stars 2 forks source link

Editor widget position and size not saved #18

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. run marave
2. move & resize the editor widget
3. quit
4. run marave again - the editor is in the default position

What is the expected output? What do you see instead?
The editor widget should be where it was last put by the user.

What version of the product are you using? On what operating system?
Marave svn r93, Kubuntu 9.10 amd64, KDE 4.3, python-qt4 4.6-1

Please provide any additional information below.
There is "Settings stored" in the terminal on exit, so I guess this should 
work.

Original issue reported on code.google.com by cyberkil...@gmail.com on 5 Feb 2010 at 12:42

GoogleCodeExporter commented 9 years ago
Sorry, I meant Marave svn r94.

Original comment by cyberkil...@gmail.com on 5 Feb 2010 at 12:43

GoogleCodeExporter commented 9 years ago
Could you post your ~/.config/NetManagers/Marave.conf ?

Original comment by roberto.alsina on 5 Feb 2010 at 1:07

GoogleCodeExporter commented 9 years ago
[General]
buttonstyle=2
lang=pl_PL
x=151
y=63
w=541
h=446
font=@Variant(\0\0\0@\0\0\0\0@ \0\0\0\0\0\0\xff\xff\xff\xff\x5\x1\0\x32\x10)
fontsize=8
click=thozi_daClick.wav
station=@Invalid()
bgcolor=@Invalid()
background=white sands.jpg
editoropacity=0

It seems to be fixed in r95 after I nuked the settings.

Original comment by cyberkil...@gmail.com on 5 Feb 2010 at 1:12

GoogleCodeExporter commented 9 years ago
OK, then, I'll just mark it as fixed and cross my fingers ;-)

Original comment by roberto.alsina on 5 Feb 2010 at 1:30

GoogleCodeExporter commented 9 years ago
Oops, now it's happening to me!

Original comment by roberto.alsina on 5 Feb 2010 at 1:32

GoogleCodeExporter commented 9 years ago
r96 brought this issue back ;-P

Original comment by cyberkil...@gmail.com on 5 Feb 2010 at 1:44

GoogleCodeExporter commented 9 years ago
Ok, got it, loading prefs in wrong order:

Loading the background caused a resize event, which , since the geometry of the 
editor was not loaded yet, caused an automatic resizing of the editor.

Later, loading the geometry, didn't cause a resizing.

So, changed the order of loading, added explicit resizing in r97, should take 
care 
of this.

Original comment by roberto.alsina on 5 Feb 2010 at 1:47

GoogleCodeExporter commented 9 years ago
Confirm, r98 is ok.

Original comment by cyberkil...@gmail.com on 5 Feb 2010 at 1:52

GoogleCodeExporter commented 9 years ago

Original comment by roberto.alsina on 5 Feb 2010 at 2:36