Bug 226371

Summary: [Patch] YaST2 Control Center doesn't remember size
Product: [openSUSE] openSUSE 10.2 Reporter: Stephan Binner <stbinner>
Component: YaST2Assignee: Stefan Hundhammer <shundhammer>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: forgotten_h13THG8RK1
Version: RC 5   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Development Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Patch to add size memory

Description Stephan Binner 2006-12-06 10:08:36 UTC
I'm getting really annoyed by the YaST2 Control Center starting up with only one column display, me adjusting its size to fit 2 or 3 columns and it just forgetting about the new size the moment it quits.
Comment 1 Stefan Hundhammer 2006-12-06 12:10:36 UTC
It starts with a default size. This is intentional.
Comment 2 Stephan Binner 2006-12-06 12:30:44 UTC
I see no sense in starting with a default size which is too small to show a reasonable amount of items for my font size or my language.
Comment 3 Stefan Hundhammer 2006-12-06 12:57:32 UTC
I see no sense in pointless reopening of overenginnered features. The default size works fine.
Comment 4 Stephan Binner 2006-12-06 15:00:09 UTC
No it doesn't, see above. This is an usability problem.
Comment 5 Stephan Binner 2006-12-06 15:51:12 UTC
Created attachment 108531 [details]
Patch to add size memory
Comment 6 Stefan Hundhammer 2006-12-06 16:11:30 UTC

*** This bug has been marked as a duplicate of bug 56094 ***
Comment 7 Stephan Binner 2007-06-14 14:34:13 UTC
Now would be a good time to commit this patch. Or to give a reasonable explanation against it.
Comment 8 Stefan Hundhammer 2007-06-14 16:49:26 UTC
This is only a very small part of it. YaST2 session management involves a lot more.

*** This bug has been marked as a duplicate of bug 58579 ***
Comment 9 Stephan Binner 2007-06-15 13:41:55 UTC
This can't be a duplicate of 58579 as that bug report is about the package-manager and this bug report is about the YaST2 control center.

What other session management beside remembering its last size is missing/desired in the YaST2 control center?
Comment 10 Stefan Hundhammer 2007-06-18 11:03:51 UTC
Yes, it IS a duplicate of that bug. 

Please stop messing around with this one. You are wasting your own and my time.

*** This bug has been marked as a duplicate of bug 58579 ***
Comment 11 Stephan Binner 2007-06-18 11:18:26 UTC
> Yes, it IS a duplicate of that bug. 

How can it? Those are different codebases, packaged into different packages (yast2-qt v yast2-control-center).

The only commonness I see is that it has the same insubordinate maintainer.

> You are wasting your own and my time.

And you have again given no reasoning against this patch or an explanation.
Comment 12 Stefan Hundhammer 2007-06-18 11:35:58 UTC
Do you really need explained what "session management" is all about?
Do you really not see the abstraction between only some package selector settings vs. everything else?

Do you really not see the host of problems a quick & dirty solution is certain to raise? Just think of details like control center running as root, but on behalf on some user; where to stort settings? What to do when things are written to ~root, yet multiple users might want different settings?

If you want to take over maintenance of yast2-control-center-qt, that's fine with me. But as long as I am the maintainer, you'll have to accept decisions about it the responsible maintainer makes. And that happens to be me.

Frankly, I am losing my patience with this behaviour of yours.

*** This bug has been marked as a duplicate of bug 58579 ***
Comment 13 Stephan Binner 2007-06-18 14:37:41 UTC
> Do you really not see the host of problems a quick & dirty solution is certain to raise?

I object that it is a quick and dirty solution and don't see such problems.

>  What to do when things are written to ~root, yet multiple users might want different settings?

Why do you invent unrealistic use cases instead of fixing this real world bug?