[V22 BUG?] - second (floating) viewer zoom influences the 'main' viewer
Setup:
I have a second monitor that I use to display some floating tools, amongst which:
- a big histogram
- a navigator
- a (second) viewer
The idea is that I can zoom this second viewer with primary view to 100% and use the navigator to pick the spot I want to view at this enlargement. The main window's viewer is set to multi view to show the selection.
The issue:
The above setup works and zoom levels are often kept, but not when unselecting all images and making a new selection or changing albums.
With the (second) viewer zoomed to 100%, when making a new selection of photos, all their multi-view 'thumbnails' in the main GUI are now zoomed to 100%.
When this is changed to a 'fit' zoom and making another selection, now the second view window also changes to fit on a new selection instead of staying 100%. It seem the main GUI's viewer and the separate view (window>viewer - F10) are linked together and don't remember their own settings.
Workaround:
Use a floating focus tool and right-click mouse to select focus point.
-
Propheticus,
Are you also reporting these matters as Support Cases via the "Submit a request" feature of the Community pages?
If not and you feel these really are bugs (rather than change requests) that should be given some attention, then I think you should assume that not much will happen to them if simply posted in a User to User forum facility.
0 -
I'm first leaving open the option that I might be a 'stupid user' and simply use the tools in ways they're not intended.
This forum allows others to either tell me where I'm wrong or try out / confirm they face the same and it's not an isolated case.If it bothers me enough and others confirm it's not just me, I'll report the issue. I've done this for the random selection of images issue.
0 -
Maybe revise the post title from [Bug] to [Possible bug?] to avoid potential confusion for forum users?
Especially random visitors who may be alarmed by a long list of apparent "Bug" reports that are not necessarily bugs at all but the title, once set for the post, will probably never ever change.
In addition, there may be confusion that leads people to think that the forum can be used for generating requests for personal assistance when the Support Process is actually undertaken through the "Submit a request"community feature.
That's something that is not well understood nor very well promoted within the community pages. Many a User has become disappointed when they receive no official response to a question that was posted in the forum only rather than through the managed support channel. Anything that tends to encourage people to believe the entire set of forum threads here is part of an official support operation is best corrected as early as possible.
(There are some officially monitored forum sections seeking feedback but these are few and should be obvious when discovered.)
0 -
I took your hint and indeed added a question mark.
To be clear, I did not expect the issue to be picked up or resolved by a PhaseOne employee here.
I do find it rather closed / non-transparent that there's no official bug reporting forum section or bug tracker.
This, combined with the high number of ui navigation/cosmetic bugs I've already encountered as a relatively new (and paying) user, does not boost my confidence.It would help to be able to see whether an issue you're encountering is just you/your installation/unicorn or that it's a broader issue. Instead of everyone having to send a full report for simple ui/browser bugs, public reports could be upvoted "I have the same issue". Perhaps users/support can post known fixes/workarounds that would benefit anyone searching for the same bug instead of having to handle them all as individual private support tickets or 'requests'.
(see for example the Adobe support community pages with a bug report section per application)0
Post is closed for comments.
Comments
4 comments