On Fri, 2 Oct 2020 16:29:08 GMT, Victor Dyakov <vdya...@openjdk.org> wrote:
>> @mrserb Can you review this? > > @aivanov-jdk Can you review this? I still suggest to try the approach recommended here: https://mail.openjdk.java.net/pipermail/awt-dev/2020-August/016074.html On 29.05.2020 14:35, Alexey Ivanov wrote: > The ultimate goal of this API could be to provide an MRI which stores all the > available icon sizes and loads > dynamically the size that's most appropriate to the current display settings. > Raymond Chen has a blog post about the > format of the icon resources [1]. If we do that, we will handle all the > scaling ourselves and will be able to define > our own algorithm for choosing the closest match. As explained in > LookupIconIdFromDirectoryEx [2], LoadIcon and > LoadImage “use this function to search the specified resource data for the > icon… that best fits the current display > device.”> [1] https://devblogs.microsoft.com/oldnewthing/20120720-00/?p=7083 > [2] > https://docs.microsoft.com/en-ie/windows/win32/api/winuser/nf-winuser-lookupiconidfromdirectoryex If an approach above works then we could request the icon of the exact existed size, and if that size is unknown we could request some predefined size like 16,24. etc Some additional comment was sent here: https://mail.openjdk.java.net/pipermail/awt-dev/2020-August/016081.html ------------- PR: https://git.openjdk.java.net/jdk/pull/380
