LR 5.x continues to be a headache. Just when I thought I solved it all, there are issues when users have subpanels hidden in the develop module. This is not that big a deal - we could just say that Paddy requires all subpanels to be open - but this whole thing just pains me.
I have an idea on how to rework Paddy's core. It will be a parallel project, but once done, Paddy should be much more flexible and faster to adapt to new LR versions. It's a lot of legwork, not that much programming. Basically, I need to map LR's user interface to be able to say "Paddy slider #100 is the 5th slider in the Panel called "details", then get the windows handle for that slider. This is just a lot of legwork (some less obvious than it appears from the panels, especially for the filters), plus some adjustment for the HSL panel, but I have reached the point where I suspect I should have done that a long time ago. It would have saved me a lot of time now.
Stay tuned, we are nowhere near the end.
I have an idea on how to rework Paddy's core. It will be a parallel project, but once done, Paddy should be much more flexible and faster to adapt to new LR versions. It's a lot of legwork, not that much programming. Basically, I need to map LR's user interface to be able to say "Paddy slider #100 is the 5th slider in the Panel called "details", then get the windows handle for that slider. This is just a lot of legwork (some less obvious than it appears from the panels, especially for the filters), plus some adjustment for the HSL panel, but I have reached the point where I suspect I should have done that a long time ago. It would have saved me a lot of time now.
Stay tuned, we are nowhere near the end.