Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
1
From what I can see now Photolab finally seems to be able to display my files the way I want it. I have a long time put the RAW-files in the topfolder of “a session” and the JPEG-derivates below in a subfolder. In PhotoMechanic, Capture One, iMatch and XnView it has been possible to see the RAW-files and the JPEG-files side by side a long time. The exception has been Photolab. I guess this is better even for those who maintain the metadata only in Photolab.
In order just to see the RAW there is a filter for displaying just the RAW
Without this feature in Photolab it has been hard to get a good overview of how metadata has been synched from PhotoMechanic and iMatch to Photolab, so this is for me very welcome.
What version of PL do you have ?
I don’t understand, you mean that you see the RAW and JPG files at the same time even though they are in different subfolders ?
Which was there already in PL1, probably also in DxO Optics Pro.
Luckily for me PL9.2.1, like previous versions, doesn’t display what’s in CurrentWorkingDirectory subfolders
Like @Franky, curious what you really had in mind…
Something like softlinks?
Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
4
Yes now I can see both the pictures (my RAW) in the topfolder and the JPEG in the subfolder at the same time side by side now and that has not been possible before. That was a thing I asked for in a request once since I saw it as a problem.
I´m not the only one having had problems with this before.
I’m not sure it’s really a problem, as I would find this behaviour distracting. If I wanted to see them both, I would put them in a common folder and set the filter for both RAW and RGB.
It’s still not clear what you mean. Let me guess – is it the possibility in ‘Compare → Select a refence image’ to choose reference image from a subfolder (actually from anywhere)? This is surely possible also in PL8.10/Win. What on earth has PhotoMechanic to do with that?
Files in the filmstrip come from the current directory ONLY, or am I wrong??
Being “dazed and confused” like Led Zeppelin.
The PL image browser is based on the Windows file browser and like it, it is unable to simultaneously display files from a folder and its subfolders. You’re using he Compare view which is something different because you can select a reference image from a different folder. This feature is not new.
However, I’m missing the “view subfolders” feature too. I’m using it very often in Lightroom. But you won’t see this in PL until DxO rewrite the image browser. This is not likely to happen very soon.
That’s the case in Lightroom and this can be enabled/disabled using a keystroke. Very handy.
This is possible only because LR implements its own folder tree. DPL apparently uses the same Windows control as the one used in Windows Explorer. I say “apparently”, because the DPL main window appears to be “Window Spy resistant”. It’s impossible to detect/explore any child window below the DPL main window which appears to the system as a big blob within which everything seems to be managed in a non standard way. Even the image browser, when undocked and living in its own independent window, cannot be detected by any window monitoring tool.
This is very strange. In much older versions, I could see that the folder tree was actually a customized version of the standard tree control used in Windows Explorer. So, I guess this didn’t change. DPL appears to embed code masking all child windows. I can’t imagine why they need to do this.
Anyway, as stated above, implementing an LR-like “dive view” feature in DPL implies reworking the whole UI. Although this is obviously necessary for a number of reasons, we all know that this will not happen in the near future.
Got it ! That’s because the DPL UI is written using WPF. This kind of UI doesn’t expose “real” child windows. Window monitors are therefore unable to find any window handle corresponding to the various UI elements (these elements are named “light controls”).
This could also explain why it’s more difficult to get a consistent UI in PL because communication between these elements is much harder to implement.
Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
14
Not necessary really because it is just to use the RAW-file filter in my case so for ne it works as I like it too.
Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
15
The fiilter is one thing and the new function where even subfolders files are displayed is another and the important here,
From a developer’s point of view, a WPF based UI is like a web page. You describe it graphically and WPF takes care of the interaction between user and program. However, contrary to “classical” development, each UI item doesn’t have its own life as a normal child window. It is not identified by a window handle through which messages can be sent in order to directly notify the program of a given event (e.g. click on a button).
If this mechanism makes possible to design more appealing UIs, there are drawbacks with this approach :
Since user actions cannot be interpreted directly, performances and reactivity might be affected.
This mechanism consumes more system resources than the classical approach.
Communication between UI elements is more difficult to manage, especially in complex interfaces, In particular, implementing the UI as a finite state machine (FSM) - which should be the case for complex UIs - becomes more difficult.
Tracking bugs in the UI is significantly more difficult.
This can probably explain some of the Ui qirks that we are regularly observing.
Good for you, and there are reasons to implement it like it is.
limited view limits the time it takes to apply presets and render the previews
limited view prevents PL from ingesting (and rendering) thousands of images, e.g. if one clicks on a root folder by mere chance
On the other hand, other users can profit from seeing every image file within the selected folder and its subfolders.
deep view allows for mass application of operations, keywords etc., but it would necessitate a smarter way to render previews than the current do-it-all
deep view is better suited for user managed import (see above)
By making PL less restricted, it could get more interesting for a wider audience. And as nothing comes from nothing, some work needs to get into such a paradigm shift. No matter how much effort that would be, DxO has/is so far stuck to its current principles.
SVP vous l’avez fait comment? Je suis aussi sur Mac! Très intéressé, c’est la seule raison pour laquelle j’utilise LR pour trouver des fichiers et réorganiser… DXO devrait vous payer pour l’astuce.
By the way, since WPF is Windows-only, we are not nearing the end of the Mac vs. Windows discrepancies.
Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
20
But that is exactly what we get now. If you select a top folder you will by default see both what is in the top folder and the subfolders.
There is a problem with this when you just want to see what is in the top folder. For me it works because I always put just the RAW-files in the top and then I can filter away the JPEG-files if I please.
What is missing is a funktion where you can turn on or off the inclusion of the subfolders. In XnView the menu option is called “Show files in subfolders” and it is under the “View”-menu which is logical.
Well, one step at the time :-).
I´m very pleased with what they have done for me now. If you and others still are not totally satisfied why not joining the Mac-users and take it even further. Concistensy over the platforms are essential. May be they even can look into the AI-interfaces because they also differs between Mac and Windows.
