Can't see values of memory view in light theme
See original GitHub issueDescribe the bug
Can’t see values of memory view in light theme. Specifically the values are made bold and white - see screenshot (further in the issue).
To Reproduce
Steps to reproduce the behavior:
- Select a “light” theme i.e. “Light+ (default light)”
- Memory view from the console:
-mv $c000 100
- The 100 highlighted bytes are white on a light background.
Expected behavior
Bold on the default font colour is used rather than white (or white hard coded).
Screenshots
Version etc. (please complete the following information):
- DeZog SW Version: 2.0.3
- OS: macOS - Big Sur (do not recommend!)
- Remote: zsim
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Dark theme not showing table values in my Android app
I've discovered the issue. I used custom styling in my table layout and set the background color of the the custom table border...
Read more >Use the Memory windows in the Visual Studio debugger (C# ...
Learn how to use Memory windows as you debug, to see the memory space your app is using. Other windows show variables and...
Read more >Enable dark theme - Chrome Developers
# Set up dark theme from Settings. Click Settings ALT_TEXT_HERE . You can also open Settings by pressing F1 . Under Preferences >...
Read more >Building a theme switch component - web.dev
For example, a user's system is in a light theme, but the user prefers the website to display in the dark theme.
Read more >Implement Dark Mode in Flutter using Provider - FlutterDevs
we are using the SharedPreferences to set the value in the memory so even if we close the app and reopens it, our...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks. Will correct that in the next release.
Fixed in 2.1.0.