You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The current implementation of Status Bar Color Control is subject to many intrinsic, unsolvable limitations, bugs and sideeffects by nature of its implementation and the capabilities of the VSCode extension API.
Describe the solution you'd like
An alternative implementation of status bar color control that only changes the text color of the status bar item (StatusBarItem.color)
With this, there is no mucking about with the user's settings.json, eliminating side effects, unexpected behaviour, and potential for performance degradation, with the trade-off that the change is not as visually pronounced.
Describe alternatives you've considered
Changing the backgroundColor of the StatusBarItem
this is discouraged by the VSCode UX guidelines and explicitly kneecapped by the extension API, presumably for this reason.
Is your feature request related to a problem? Please describe.
The current implementation of Status Bar Color Control is subject to many intrinsic, unsolvable limitations, bugs and side effects by nature of its implementation and the capabilities of the VSCode extension API.
Describe the solution you'd like
An alternative implementation of status bar color control that only changes the text color of the status bar item (
StatusBarItem.color
)With this, there is no mucking about with the user's settings.json, eliminating side effects, unexpected behaviour, and potential for performance degradation, with the trade-off that the change is not as visually pronounced.
Describe alternatives you've considered
backgroundColor
of theStatusBarItem
StatusBarItem.color
can be set to an arbitrary color orThemeColor
.Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: