i open for the fist time digikam then the windows is contained in the sceen then i click at the right on the map icon then the windows increases its size to the right over the screen then i tried several things but i's impossible to have the windows in the screen limits then it's hard to use digikam Reproducible: Always
mageia 2 beta 3 x86-64 kde 4.8.2 digikam 2.6 b3
Hi Philippe Can you please attach a screenshot for reference? Smit
Created attachment 70524 [details] window over screen limits
i checked this is the case with virtual and real pc
It's not reproducible here under Mageia2 but in English. Please swith application from French to English and confirm. I suspect an i18n string size problem... Gilles Caulier
(In reply to comment #5) > It's not reproducible here under Mageia2 but in English. Please swith > application from French to English and confirm. I suspect an i18n string > size problem... > > Gilles Caulier yes no oversize pb with english version
Created attachment 70526 [details] window not over screen limits with english version
also we can't resize inside windows of digikam : - album tree - photos - data
digikam 2.6.0 rc pb still there
kde 4.8.4 digikam 2.9.0 pb still there
I am using KDE 4.9.2 "release 511", DigiKam Version 2.9.0 in English and I can confirm the window is not larger than my current screen resolution. I too suspect of i18n issues. Philippe, what do you mean by "we can't resize inside windows of digikam"? Are you talking about the vertical pane? If so, I believe there should be a QSplitter in there and it should be a matter of setting a smaller number for the minimumSize property for each component in where Album, Photos, Data, etc are loaded, in case we are talking about the same thing here. Regards.
>> Philippe, what do you mean by "we can't resize inside windows of digikam"? inside the digikam windows there are 3 windows : left (albums), center (photo) and right (properties) we can't resize horizontally these windows also we can't resize horizontally the digikam window according the window is in the screen limits
I cannot reproduce the bug. In my install I can horizontally resize the 3 mentioned windows, but again it feels a bit rough when doing that in the left and right windows. I really believe a smoother feel will be achieved if a small minimumSize property is set (I wonder if a developer can check that out). I guess the minimumSize property will also have its effects when the digiKam window is located in any of the screen limits. Regards.
i have just made some experiments for each window i can maximize or minimize its horizontal size but there is no choice of the size only max or min(no more window) one
i remember with previous versions i had the ability to choose the horizontal size of the windows as any type of kde windows for example the digikam window
For the other pb : oversize screen limits i have no more pb strange !
mageia 3 a3 x86_64 digikam 3.0.0 beta 3 again : windows oversize screen limits ! but with special feature : digikam window is not over screen limits but the contents is over digikam window ! no pb in english
i found where is the pb seen by user : - this is around window size settings, it seems digikam have bad size settings - using in kde xrender you must have an adapted size setting - using in kde opengl you must have an adapted size setting - adapted size settings are not the same for xrender and opengl - with adapted size settings there is no more pb but why in english digikam ahve the good size setting and not with french ?
>but why in English digikam ahve the good size setting and not with french ? Because the string sizes used in label are not the same (:=))). QLabel widget has a static size set to strings char size taken from translations. In special case we can use another widget from KDElibs to prevent this problem, but this cannot be generalized else GUI will be unsuitable... Typically, i see that English strings are in general more short than French translations. This is why English version work better (and i use EN instead FR on my computer) There is also a responsibility to translator to generate short string in case of GUI layout is broken. Typically, when you translate GUI, you must check if translations don't break layout. Because free time do not permit this translator generally shortcut this stage... (just my experience as KDE FR translations coordinator in 2002-2003 (:=))) Gilles Caulier
(In reply to comment #19) > >but why in English digikam ahve the good size setting and not with french ? > > Because the string sizes used in label are not the same (:=))). QLabel > widget has a static size set to strings char size taken from translations. > In special case we can use another widget from KDElibs to prevent this > problem, but this cannot be generalized else GUI will be unsuitable... > > Typically, i see that English strings are in general more short than French > translations. This is why English version work better (and i use EN instead > FR on my computer) > > There is also a responsibility to translator to generate short string in > case of GUI layout is broken. Typically, when you translate GUI, you must > check if translations don't break layout. Because free time do not permit > this translator generally shortcut this stage... (just my experience as KDE > FR translations coordinator in 2002-2003 (:=))) > > Gilles Caulier Therefore, this bug should be fixed by contacting the French Translation Team? Regards.
opensuse 12.2 x86_64 fresh install with virtualbox digikam 3.0.0 i open for the first time digikam : see digikam_initial.png then i clik on "full screen button": see digikam_full.png then i click on "properties" button in the right vertical tool bar : see digikam_properties.png then i switch to English : see digikam_english.png
Created attachment 78008 [details] first digikam opening
Created attachment 78009 [details] full screen
Created attachment 78010 [details] oversize
Created attachment 78011 [details] digikam in english
note : this time i have the pb with the "properties" button then it is not linked to the geolocation widget but mainly with a more general pb
typically located in digiKam translations... Gilles Caulier
- as already descripted in comment #8 i can't resize windows insides digikam windows. i can only minilmize them. - i can workaround the pb by forcing the size of the digikam window - digikam window has overscreen size i assume another hypothesis : in digikam there is a pb about using qt procedures around sizing windows. the english-french feature reveals the pb and masks the pb and is just a redondancy.
opensuse 12.3 x86_64 kde 4.10.1 digikam 3.1.0 same pb see the capture digikam310.png
Created attachment 78197 [details] digikam 3.1.0
There are a few switchable sidebars on the left and on the right, not only "Albums" on the left and "Properties" on the right. I guess, one of these sidebars are too wide, and Qt measures the minimum allowed width by the widest sidebar stacked. (In reply to comment #24) > Created attachment 78010 [details] > oversize
in digikam310.png do you see at the right side the strange vertical grey,white,blue ribbon ? this does not appears on my screen.
I can't reproduce. I built Digikam from git, master branch and when I open it (first opening) I only have 2 panes ("Mes albums" where no albums is selected, left pane and as right pane "Vignettes" where the Welcome text is displayed and when I click on "Carte" then the map replaces the "Vignettes", I don't have 3 panes. Maybe it's because I use the git master version which is development of 3.2? I don't see which branch build or how to reproduce the problem.
Created attachment 78256 [details] Digikam first start for me This is how Digikam starts for me with a new user, master git from 20th February 2013.
Anne MArie, Click on one icon from the left side bar, and 3th pane will appear. Gilles Caulier
hello i found another pb when someone assumes this is a french language pb https://bugs.kde.org/show_bug.cgi?id=314831
Some labels has been reduced. Please re open if you still have issue with last release. Regards
last release of what ? digikam or kde i18 fr and what release ? thanks
Of both.
*** Bug 330085 has been marked as a duplicate of this bug. ***