| Summary: | KStars for Mac OSX Issues With Colour Schemes (Switching/Saving/Displaying) | ||
|---|---|---|---|
| Product: | [Applications] kstars | Reporter: | kde.org |
| Component: | general | Assignee: | Jasem Mutlaq <mutlaqja> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | macOS (DMG) | ||
| OS: | macOS | ||
| Latest Commit: | https://commits.kde.org/kstars/a8b5c118ad4615b698c629af7d700bb31ca39f6b | Version Fixed/Implemented In: | |
| Sentry Crash Report: | |||
|
Description
kde.org
2017-07-15 13:35:37 UTC
Had a quick test on KStars 2.7.8 under Ubuntu and initial tests show at least some of the same issues. e.g. Under menus, Settings>Configure Kstars>Colors, select DEfault Colors (scheme) and then Save Current Colors ... to scheme e.g. test (to duplicate default colours). change e.g. Horizon colour to RGB(32,64,32) and watch displayed opaque horizon change to RGB(32,64,32) - as expected. Click back on Default Colors scheme and see horizon change to Default Color (as expected) then click back on test colour scheme and note that horizon does not change to the color for that scheme (RGB(32,64,32)). I've not gone through it all extensively but I suspect it (or most of it) is not just Mac version Git commit a8b5c118ad4615b698c629af7d700bb31ca39f6b by Jasem Mutlaq. Committed on 20/07/2017 at 14:50. Pushed by mutlaqja into branch 'master'. Partial fix for the color scheme bug. Now you can save an existing custom color scheme. Needs testing. The issue is not Mac related. M +27 -23 kstars/auxiliary/colorscheme.cpp M +23 -4 kstars/options/opscolors.cpp M +3 -2 kstars/options/opscolors.h M +19 -107 kstars/options/opscolors.ui https://commits.kde.org/kstars/a8b5c118ad4615b698c629af7d700bb31ca39f6b |