That _ is important: Let NPP loading other UDLs in prior of preinstalled file. Simple Put a dark UDL and name it markdown._. Happy ending: Users move or copy the existing UDL files to the dark mode folder. NPP should update the opened documents when dark mode or color tone is changed. Otherwise, load the UDL file in (fallback, default, whatever). If NPP match a UDL in dark folder, use that. Create 1 more folder when app is updated/installed. Happy ending: Users don't need to switch multiple setting windows. Another example: When user change the theme, user_selected_theme_dark is updated, but not user_selected_theme(_light?). For example: When user clicks dark mode to be enable, NPP will immediately load the value in user_selected_theme_dark in background. When dark mode is triggered, NPP will automatically update the user-selected theme in Style Configurator (Assume that user had opened the window). User don't need to click things to make it happen. 
For NPP, there are 2 setting variables: user_selected_theme(_light?) and user_selected_theme_dark.In Preferences - Dark Mode, users can select 1 syntax theme for dark and 1 for light.There will be user-selectable syntax themes: 1 for dark (apply to all tones), and 1 for light.There will be 2 main categories: dark mode and light mode.To make it simple and easy to understand for user: Manually change configs in UDL may be too complicated for users, especially when they update their UDLs in bulk.
Pre-defined dark/light in UDL does not work either.User may want to use a dark theme in light mode.So, it is not good to integrate different UDLs in one file.Users have their favourite themes in light and dark, and the themes are most possibly from different authors.You may want to create tones for light mode in future.
In contrast of syntax themes, users may often switch between dark mode and light mode (when dark mode is disable). There are 3 windows related to color appearance:.
0 kommentar(er)
