This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hello coder fellows, I am using the free edition Web Workbench for the first time today, and I have experienced an interesting issue in version 3.2.814.22544 with Visual Studio Ultimate 2012 version 11.0.51106.01 Update 1. If that helps, my OS is Windows 8 Pro. I have installed this version from the VSIX package that I downloaded from the site; not from VS Extensions Manager. I am sure that this is caused by Web Workbench because I have disabled one extension at a time until I get my accents working again. Then enabled the extension again, and the issue persisted. I tried uninstalling the extension and installed it again from the VSIX package, and the issues persists. The thing is that I can't use accents when editing Sass/SCSS files with my Portuguese keyboard. I've already tried Spanish and French keyboard layouts in the same computer and also couldn't use accents. In order to insert an accent in a vowel in Latin language keyboards, user must first press the accent key and later the vowel key. For instance, to type: à - I have to first press ~ (tilde) and then A, then I'll have à as output. Whenever I press any accent key (~ ´ ` ^), instead of waiting for the vowel, it's outputted the accent itself twice. When I type tilde, the output is ~~, and I am unable to put the accent in any vowel. The same happens with any other accent. This happens only when editing files with .scss extension and the Web Workbench extension is enabled. Ok, I use accents only in comments and that won't kill me. I can survive well without them. But comments are a lot more beautiful with correct punctuation of course. :) I hope this description might helps in order to confirm and possibly fix this issue. If anybody need any extra info, just ask me and I'll be pleased to help. Thanks in advance. Regards, Filipe Oliveira |
|
|
|
|
Thanks for reporting this - this was a bug and I have added a fix which should correct this behavior which will be available in the next nightly build (and next gallery update). Let us know if you continue to see a problem after installing the next update.
|
|
|
|
|
Thanks for your kind attention, Jeremy. I'd love to check the nightly build but I'm in such a hurry with business, so I'll wait anxiously for the next gallery update. Thanks very much. Regards, |
|
|
|
