Change color of Status Bar - NEO active connect #138
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Addresses issue# 124- Change color of Status Bar based on status of NEO connection
robliou
changed the title
|
The settings.json file is for the local developer - in this case, the DevTracker developer (i.e. you or me) not the DevTracker user. You'll need to define new color contributions for the neo status bar |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I added code to the settings.json file which changes the colors on the status bar at the bottom of the VS Code border based on Active Chain Connection status. It is currently set to orange to when it is disconnected to the chain, white when connecting, and green when NEO is connected. We can set the colors as we like and is quite eye-catching to the user.
Note that this is in response to UI issue #124 as brought up by Erik. However, per further discussion with him, it seems to have opened up a can of worms as to what 'active connection to a chain' really entails. See issue #137 for discussion therein.