MikeTO Posted August 4, 2024 Posted August 4, 2024 Choose View > Grid and Axis... Click the Grid Lines colour sample, choose HSL Colour Wheel if it's not already selected, and change the colour While the colour popup is still open (the bug won't occur if you dismiss it first), type into the colour hex value field and press Return or Tab - nothing happens with Tab and with Return you must click back into it and press Return a second time for the change to be applied Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.5, MacBook Pro (M4 Pro) and iPad Air (M2)
Dan C Posted August 8, 2024 Posted August 8, 2024 Thanks for your report @MikeTO! Interestingly I think this is a redraw issue with the grid itself, rather than an issue with the dialog not accepting the value on the first try. After typing the HEX code and pressing return once - the Colour Wheel will 'jump' to the correct location for this colour, and you can see the Grid Lines Colour Well changes to this colour also, but the guides on the canvas remain as the previous colour set. At this point, you can press return/tab in the field once again to force update the grid lines to be this colour. However, you can also skip this second return and simply zoom on the canvas. This force redraw will then correctly show the colour of the HEX value you applied to the grid. The same issue occurs for all input fields in this dialog, regardless of the Colour input method selected. For example typing values in the CMYK sliders, or using a HEX code in the RGB Hex sliders, etc - which is why I think this is considered as a redraw issue and not a UI input issue. I will be logging this with our team now, as I can't see anything related already reported, and it does not occur on Windows. I've also noticed that invalid HEX codes are treated differently per platform. For example entering the HEX value 8888888888, provides the following results: Windows - 888888 macOS - FFFFFF Windows appears to truncate the value at the 6 digit mark, whereas macOS will always default to FFFFFF for an invalid HEX. I'm getting this logged separately also. I hope this helps MikeTO 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.