| Summary: | JJ: Initial window size is too small | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Dik Takken <kde> |
| Component: | Usability-Ergonomy | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | caulier.gilles, mailinglist, marcel.wiesweg |
| Priority: | NOR | ||
| Version: | 0.7.2 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 0.10.0 | |
| Sentry Crash Report: | |||
|
Description
Dik Takken
2005-04-03 12:40:09 UTC
It's worse: The window size of the image editor is not remembered. I have to resize it every time again. Can not reproduce #1 Hmm.. I can't reproduce Comment #1 either... Must have been a glitch in the Matrix... :) Is this problem is solved for you now with current implementation ? Gilles Caulier The window is now approx. 400x300 pixels small by default. Way too small for my taste, is this the way it should be? Using DigiKam 0.8.1. wel, i think this size is automaticly computed by kdelib. I can force it to max size but i don't know if this way is right... Too, i receommend you to check the new implemention from trunk svn branch. A lots of changes/improvements/bugfix have be done. There are some fresh screnshots available at web project page. Take a look... Actually, we finalize the implementation to prepare the first 0.9.0-beta1 Gilles Caulier > wel, i think this size is automaticly computed by kdelib. Then I guess you should re-assign this report to KDELibs? > Actually, we finalize the implementation to prepare the first 0.9.0-beta1 I will emerge it as soon as it hits Gentoo Portage. I believe you can assign "Special Window Settings" to any application handled by KWin so that the geometry of the application is remembered every time it is started. For example, the default size Kopete opened with was way too small for me, so I right-clicked the toolbar >> Advanced >> Special Window Settings. Then, I just entered the size I wanted it to open with and set the combobox to remember. I wonder if that fixes this problem. ~Jahshan > I believe you can assign "Special Window Settings" to any application handled by KWin
Yes, you can. But any application should automatically pick a sane default window size when it is first started. It should not be too hard for KDELibs to see that a default main-window size of 400x300 on a 1024x768 screen is a bit ridiculous.
This is still in the junior jobs section. Is this something that is still a problem? If so, I may take a crack at it. If not.... Haven't tried KDE 4 yet... I could never confirm this for any KDE3 or KDE4 version of digiKam. Actually this is related to kdelibs. We should either close this one or re-assign it (although I don't think that this is a common problem, might be system-specific in that case). Andi Andi, I'm agree that i window sizes are driven properly for KDE3. For KDE4, it still a little problem only with Album GUI when window is maximized : the size is never restored between sessions, excepted is the window size is not maximized... I'm alone to to see this dysfunction ? I have hack this problem indeep, and fixed all others digiKam windows (Light Table, Image Editor, CameraGUI) with success, but main window still bugous. Gilles Caulier I just re-checked this and yes, it happens for me in KDE4 now, too. But not only in the main window, every window (editor, lighttable...) does this. What works: It remembers the size and position when the window is not maximized. What doesn't work: When window is maximized and closed with those settings, on next startup the window will be positioned somewhere on the desktop with a rather small size. I still think this is KWin stuff, I had this problem (and still have) with firefox and any GTK based app running under KDE, but also with native applications like amarok and kmail. Marcel, Before to re-assign this file to KDELibs, can you reproduce it with KDE4 from trunk ? Gilles (In reply to comment #14) > I still think this is KWin stuff, I had this problem (and still have) with > firefox and any GTK based app running under KDE This is also true for KDE3. I wonder if this is a KWin issue why it was not fixed for years now? Like the original poster said: This happens a lot in KDE, not only in digiKam. Andi Important: I have upgraded to OpenSuse 11.1 yesterday. Since then the window size of all windows is saved even if maximized. Default window size (width/height removed from config file) is constantly two thirds of desktop with, height varies between 400 and 667 on a 800px high display. These results were taken for the main window and the image editor, running digikam 0.10 under KDE3 and under KDE4. Marcel, Thanks for the report. Andi, Here, I don't have a computer with KDE 4.2-beta2 to test. And you ? Gilles No, I have 4.2 as well. Archlinux has not updated yet, maybe they are busy with Chakra project...? I will check out some unstable repo though and see if it is in there already. Andi (In reply to comment #19) > No, I have 4.2 as well. I DON'T have 4.2 as well Note: My kdelibs is 4.1.3 but you never know what was patched/backported by Suse. I tested openSUSE 11.1, but it comes with KDE 4.1.3, so actually the same setup as my archlinux installation. I'll need to wait to have the devel packages in archlinux I guess. Andi The window size seems to be saved correctly now, I'm running a daily snapshot of KDE here. Andi, Look here : http://bugs.kde.org/show_bug.cgi?id=178191 Why this file is not closed yet well ? Gilles Caulier I don't know :-) At least it seems to work with digiKam now. Just tested it again. Andi Marcel, Can you confirm this point using a fresh KDE 4.2 ? If yes, please close this old file definitively (:=))) Gilles Caulier I plan to install KDE4.2beta packages in the next days, but for now I tested with 4.1.3 only. I have everything working now on my machine, that is all three points above are fixed. There is a bugfix patch for libkexiv2 that I will attach here. I think it is ok to commit this to trunk and backport to the 4.2 branch, as it is only bugfix. But I'm not absolutely sure. The problem is that when using xmpData.add for XMP String Bags and Seqs, somehow values are only added and not removed. The API-changing patch that I sent to you will have to go to DMetadata as I understand this. It's prepared and ready to commit. It is suboptimal but we are late. (We could commit to trunk/ again, but, as 0.10 will depend on 4.2 only, that would mean more #ifdefs in our code, and probably we wont want to depend on KDE4.3 but only on KDE4.2 for a longer period.) Sorry, wrong browser tab. This was not at all meant for this bug. It's too late at night.. About #25, As i have a new computer installed with KDE 4.2, i can confirm that windows size is saved and restored beetween session, especially if you is maximized. I close this file now. Gilles |