XPost: misc.phone.mobile.iphone, alt.comp.os.windows-10   
   From: mariasophia@comprehension.com   
      
   Herbert Kleebauer wrote:   
   > On 2/19/2026 9:06 PM, Maria Sophia wrote:   
   >   
   >> To add value so that this becomes a useful reference for all three common   
   >> platforms, Android, iOS and Windows, here's a quick summary of details.   
   >   
   >   
   >> 2. Windows notes:   
   >> Windows supports solid colors natively, but the GUI color picker:   
   >>   a. does not accept HEX directly   
   >   
   > In Win 10/11 you can directly enter the hex values.   
   > Win10 screenshot: https://onlib.de/temp/back.jpg   
      
   Hi Herbert,   
      
   Thanks for pointing that out where you are absolutely right that Windows 10   
   and Windows 11 *do* allow direct HEX entry in the Custom Color dialog. Your   
   screenshot confirms it, and that is useful information for anyone running a   
   modern Windows build. Thank you for clarifying what I misspoke about prior.   
      
   Digging into it, the only nuance perhaps worth adding for completeness is   
   that not all Windows installations expose the HEX field the same way:   
      
   a. Older Windows 10 builds apparently did not initially show the HEX box.   
   b. Some OEM-customized Windows images hide or replace the default color UI.   
   c. Windows 7/8 never supported HEX entry at all as far as I could find out   
   d. Even on Win10/11, the HEX box only appears in the "Custom Color" dialog,   
      not in the main background settings panel.   
      
   So the statement should probably be refined to something more akin to...   
      
      "Windows 10 and 11 support direct HEX entry, but earlier versions and   
       some OEM builds do not."   
      
   That keeps the PSA accurate for everyone, regardless of which Windows   
   version they are on.   
      
   Your correction is appreciated as it helps make the reference more precise.   
      
   >> 6. Imagmagic command syntax:   
   >> This works on Windows, macOS, Linux, Android (via Termux), etc.   
   >> but I could find no native, user-installable version of ImageMagick for iOS   
   >> or iPadOS so only iOS can't do what all other operating systems easily do.   
   >>   I. Create a solid-color PNG from a HEX value:   
   >>      magick -size 1x1 xc:"#ABCDEF" solid-abcdef.png   
   >>    II. Scale it to device resolution:   
   >>      magick solid-abcdef.png -scale 2360x1640! ipad-2360x1640.png   
   >   
   > No need to install Imagmagic to generate a monochrome picture   
   > of screen size. There should be a web browser available on any   
   > phone/tablet.   
   >   
   > - Create a html file with this content:   
   >       
   >    or use this one: https://onlib.de/temp/1.html   
   >   
   > - open the html file in a web broser   
   > - make a screen shot   
   > - open the screen shot and zoom in until only the color is displayed   
   > - again make a screen shot   
   >   
   > Now you have a picture of the size of the screen with only one   
   > color which you can use as background image.   
      
   Thanks for jumping in with improvements. I always appreciate when someone   
   adds something concrete that helps make the reference better for everyone.   
      
   Your HTML trick absolutely works in the sense that it produces a uniform   
   color on the display, and for many people that is "good enough" because   
   the screenshot ends up being a solid block of pixels. It is a clever   
   workaround and it is nice because it requires no tools beyond a browser.   
      
   There may be technical caveats worth pointing out so readers understand   
   the tradeoffs:   
      
   1. A screenshot is never a mathematically pure solid color.   
      a. It can contain EXIF or metadata depending on the platform.   
      b. It may contain compression artifacts (e.g., iOS apparently uses   
         JPEG for screenshots in some cases, PNG in others).   
      c. It may contain scaling artifacts if the browser UI or zooming is not   
         pixel-perfect.   
      d. It may contain color-space tagging (Display P3 vs sRGB).   
      
   2. A screenshot is device-dependent.   
      a. The resulting file is tied to the exact screen resolution.   
      b. It may include color-management adjustments applied by the OS.   
      c. It is not guaranteed to be identical across devices.   
      
   This matters mainly for people who want:   
      a. a mathematically perfect solid color,   
      b. a wallpaper with zero entropy for privacy,   
      c. a file that is identical across platforms,   
      d. a file with no metadata, no EXIF, and no compression noise.   
      
   That is why the 1x1 PPM -> PNG method is still a more precise and   
   platform-neutral way to generate a true solid-color wallpaper. It produces   
   a file that contains literally three bytes of color data and nothing else.   
      
   But your HTML method is still very useful for people who want a quick,   
   no-tools solution, especially on platforms like iOS where command-line   
   tools are not available. So thanks for adding it to the toolbox.   
      
   The more options we give people, the better the reference becomes.   
   --   
   Intelligent people can always come up with many solutions to any problem.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)