V8. Grid no longer floats behind image

,

I don’t know if I’m alone in finding this an annoyance. Before version 8, if you zoomed in and panned the image, it moved above a fixed grid. I found this useful when performing manual perspective changes including rotation; dragging the image until a proposed horizontal or vertical was adjacent to a grid line. Now, the grid is panned with the image which makes my use case difficult (I have to find a zoom amount that brings my image lines somewhat near to a grid line).

I have brought this to DxO’s attention but have not received a response other than a ‘how was your experience’ automated reply,

David,
Just checked this with PL8 (version 8.1) and PL7 (version 7.10) and find the changed behaviour of the grid when the image is zoomed is just as you describe. I hadn’t noticed this until you mentioned it, so I guess it’s not something that bothers me too much - other than being an example of where behaviour changes appear to be arbitrarily introduced without any stated rationale, or even announcement of the change.

Yes true, I didn’t know this.

But I would very much prefer a grid adjustable in percentage values, then always “covering” the long as well the short side of the pic.

Oh yes, that’s right.
I’m used to playing with the screen zoom to align grid and image.
Now, it’s a cat-and-mouse game !

To my knowledge this has never been requested.
I’ll make a request.

Pascal

1 Like

I just tested it myself and I agree that the previous implementation of the grid is more useable. I don’t know why it was changed but DxO often makes subtle undocumented changes from year to year for unknown reasons. Sometimes they are improvements, but just as often, they are not.

Mark

I used to have full head of hair, the first time I requested a percentage grid, back in the OpticsPro days. The current sizing is quite arbitrary and unpredictable. A percentage grid would make a centred gridline possible. Again I would find that useful for perspective - correcting verticals in the centre of the image is often a good start.

Looks like this must be a Win only problem. On my Mac, in every version for PL1 to PL8, the grid doesn’t move or resize at all.

I hadn’t noticed this change either, so it seems it hasn’t affected how I use the grid (yet). I checked the pdf User Guide, which says

You can also configure the grid:
Mac: Preferences > View tab to change the size and color, or use inverted colors.
PC: Preferences > View > Customize tab.

…but that’s not what’s in Edit/Preferences…
And the View tab only allows turning the grid on or off (same as Ctrl-G).

I sent a message to DxO Support about this.

Thanks, everyone. I noticed only yesterday that something had changed with the grid and couldn’t make sense of it. I remember having to zoom in and out to align the grid with what I was trying to align - and now it seems harder to do. But I can change the grid spacing (“overlay grid size”) by selecting Edit > Preferences > Display (Windows 11).

an example of what it looks like with a custom percent grid

  • grid @ 33.33%
  • divided by 4 lines (normal, dotted, …)
  • custom color

And should the grid scale with the image or with the zoomed frame size?

The grid should be a property of the window, not the image.

George

In that case, that is what the Mac version does and, as far as I can tell, always has done since, at least, PL1.

That’s what it does in PL7 and earlier, windows. In PL8 it’s a property of the image, it’s moving with the image and becomes unusable. Must be a bug.

George

2 Likes

The only use case of “property of the image” to my mind would be as a cropping aid, which is provided by the cropping grid.

So yes, definitely property of the window. As stated elsewhere, it’s a bug in Windows version 8 as all previous versions were ok.

Hi

DxO replied to my request.
“This bug has been identified by our developers and a fix will be available in a future update.”.

Pascal

2 Likes

Thank you for the update Pascal.

I reported this to DxO a while back but didn’t get any response so my thanks for bringing it to their attention. With each update, I check to see if has been fixed but no fix as at Windows 8.2.1 Build 487. Hopefully soon.

David

1 Like