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
|
When using SASS CSS files (extension .scss) without Mindscape Workbench the VS2012 intellisense works as normal (because I added file extension .scss to be processed by the standard CSS Source Editor. So far, so good. No when I enable Mindscape Workbench (and remove the file association above) all the standard intellisense is gone and all I get is a list of variables. For example, typing
it brings up the list of $variables defined at the top of the file but no list of real colours that I might want to use (and which tell me whether I've spelled it correctly). So it appears the Workbench intellisense is expecting me to know all the possible css properties off by heart as I'm not going to be adding SASS variables onto each CSS property. Have I overlooked something or is this the intended behavious of Workbench? |
|
|
|
|
No this isn't the intended behaviour, the list of available CSS properties should be being shown in addition to any mixin's and variables that are available in the current scope. Can you confirm what version of WW you are using?
|
|
|
|
|
The version of Workbench is the free version: 3.2.703.22309 (with VS 2012). Hang on, VS2012 has just come up with an update: 3.2.748.22436 but this hasn’t cleared the problem. Screen shot attached. I only see ‘mainColor’ in the drop down Intellisense suggestions. [Attachment] |
|
|
|
|
I can confirm having the same sort of behavior for the licensed version, same build '3.2.748.22436' |
|
|
|
|
Ah sorry, I see you are actually referring to the property values rather than property name. No, this is correct then, we dont currently provide any hinting as to possible values for CSS properties other than providing variables which are in scope which could be used. We are looking to leveraging more in VS2012 in the future now that they have some native value editors available for CSS but this is not something we currently provide.
|
|
|
|
|
In that case I'd rather have the native VS2012 intellisense re-enabled for CSS properties (I can remember a few variable names but not all the CSS variants). Is there any way to switch off the Workbench intellisense whilst retaining its colour-coding and removal of the squiggly red lines that VS2012 puts there (as it doesn't understand SCSS)? Perhaps it's just that I haven't yet got VS2012 to play nicely with SCSS file syntax - anyone else out there managed this? |
|
|
|
|
Sorry no this isn't currently possible, but as I mentioned we are looking at taking advantage of the VS2012 editor enhancements in the future.
|
|
|
|
|
This is pretty disappointing. Otherwise, I absolutely love your product - but the lack of the vs2012 property-value intelligence (that I'd just gotten used to) is very inconvenient. Really looking forward to that change. That, and when you hit enter after certain SCSS features ( e.g. &:hover ) it autocorrects to a seemingly arbitrary $variable. |
|
|
|
|
I have to agree that VS intellisense is a must have for CSS properties. I love your product, but without property value intellisense, writing SASS becomes harder than writing CSS. |
|
|
|
