Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The current patch in the patch map should be highlighted #839

Closed
hhyyrylainen opened this issue Sep 23, 2019 · 1 comment · Fixed by #858
Closed

The current patch in the patch map should be highlighted #839

hhyyrylainen opened this issue Sep 23, 2019 · 1 comment · Fixed by #858

Comments

@hhyyrylainen
Copy link
Member

Right now it looks the same as the other patches. The border colour should be changed to indicate it is the current patch.

Dak2896 added a commit that referenced this issue Sep 27, 2019
* Current patch is highlithed.
@hhyyrylainen hhyyrylainen added this to the Release 0.4.3 milestone Oct 5, 2019
@hhyyrylainen
Copy link
Member Author

This is basically already fixed in: #858
That just needs one small tweak before merging.

hhyyrylainen pushed a commit that referenced this issue Oct 13, 2019
* #855 fix

* TypeError no more show, caused by display none called before changing values

* #839 fix

* Current patch is highlithed.

* Remove line

* By mistake i add this, it's useless, so remove it

* freeBuild fix and currentPatch after move

* FreeBuild allow moving in more patches
* Current patch is updated after moving

* RunCodeFormatting.rb

* Better code explanation

* Solve name of variable issue

An event  called `event` is created after so we need different varaible name

* Update microbe_editor.as

Also vars canno have same name.

* requested fixes

* Current patch changes

* Add inner border instead of outer border for current patch
* Change curent patch color from blue do green

* CSS border fix

* codeStyle fixes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant