Bug 321122 - ImageView/ShowLockZoomButton does not work when viewing in Full Screen
Summary: ImageView/ShowLockZoomButton does not work when viewing in Full Screen
Status: RESOLVED DUPLICATE of bug 334530
Alias: None
Product: gwenview
Classification: Applications
Component: general (show other bugs)
Version: 4.10.4
Platform: Ubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: Gwenview Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-13 16:43 UTC by Diogo Vinicius Kersting
Modified: 2014-08-16 14:27 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Diogo Vinicius Kersting 2013-06-13 16:43:35 UTC 
I configured ImageView/ShowLockZoomButton directly in conf file, and the "lock" works perfectly as long as I'm not in fullscreen.


Reproducible: Always

Steps to Reproduce:
1. Configure  ImageView/ShowLockZoomButton=true in your conf file.
2. Start gwenview and "lock" the padlock icon in the bottom right corner.
3. set the program to fullscreen (Ctrl+Shift+F), and change the zoom level of the open image.
4. go the next/prev image. You'll see that the zoom level was reset.

Actual Results:  
Zoom level reset when going the next/prev image.

Expected Results:  
Zoom level manteined when going the next/prev image.

Gwenview 4.10.2 (Debian Experimental)
Comment 1 Benni Hill 2013-06-13 17:33:52 UTC 
Confirmed with 4.10.4 on Kubuntu. Thanks.
Comment 2 Christoph Feck 2014-06-02 15:56:06 UTC 

*** This bug has been marked as a duplicate of bug 334530 ***
Comment 3 Felix Miata 2014-08-03 11:51:47 UTC 
This is the newer, thus 334530 is the duplicate by the very definition of duplicate.
Comment 4 Christoph Feck 2014-08-16 14:27:24 UTC 
I see no reason why duplication must follow the age rule. Newer bugs sometimes have more information, such as better description, more opinions in comments, recent patches, etc.

Bug 334530 additionally references changes after bug 321122 was reported, it has more votes, and has a higher severity.