-
Notifications
You must be signed in to change notification settings - Fork 0
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
[CLOSED] Couzteau issue1241 #1548
Comments
Comment by jasonsanjose Reviewing |
Comment by jasonsanjose Looks like there are some additional references that use Initial review complete. |
Comment by couzteau Sure - will make the changes. |
Comment by couzteau Thanks for the through review - i was rushing it a bit this morning |
Comment by couzteau
Note - I redefined the code as the brackets uses 187.
|
Comment by RaymondLim
I googled on VK_EQUAL and found out that there are two camps. So I'm okay to keep it as is. BTW, there are some hard-coded key codes in CodeHintManager.js that you need to replace with your changes too. |
Comment by couzteau Thanks Ray - I'll take a look at Code hinte manger as well as the tests and update the pull request. |
Comment by jasonsanjose Hi Jochen. Looks like you need to sync up with master before we can merge. |
Comment by couzteau Thanks for the info - won't get ti it before tonight. |
Comment by jasonsanjose
|
Comment by couzteau done |
Comment by jasonsanjose Thanks. Merging. |
Comment by couzteau Yay! Thanks -my pleasure. |
Issue by couzteau
Friday Sep 07, 2012 at 16:40 GMT
Originally opened as adobe/brackets#1583
Hello Brackets people,
Happy to make a stab at my first contribution. :)
All keycode references in src should be updated. All tests are passing.
I have not updated all tests to use the new module yet, but would be happy to update them soon.
Got to get to my day job ;)
Not sure if you like that I added some KeyCode definitions that are not defined here:
http://www.javascripter.net/faq/keyeventconstantsfirefox.htm
Those listed below are not defined in the , as IE deviates from other browsers. Since brackets uses them I added them following the same naming convention as other key codes. We may want to use a different prefix rather than DOM_VK? to stay consisten Happy to change if you prefer.
DOM_VK_SEMICOLON: 186,
DOM_VK_EQUALS: 187,
DOM_VK_COMMA: 188,
DOM_VK_DASH: 189
Adding them in required to remove definition defined the reference doc above:
DOM_VK_EQUALS: 61,
DOM_VK_SEMICOLON: 59,
I have not updated any key code references in sources in 3rd party or extensions.
Jochen
couzteau included the following code: https://github.com/adobe/brackets/pull/1583/commits
The text was updated successfully, but these errors were encountered: