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
|
I have the pro version, but this never worked for me. I disabled all my VS addins & extensions, but it still does not work. Syntax highlighting & comment/uncomment do work however ..any ideas? Tnx |
|
|
..bump no function signatures or intellisense.. |
|
|
Can you describe more precisely what you are doing? E.g. what is the sequence of keystrokes that you are expecting to bring up signature help and isn't doing so? This is working when we test it but perhaps we are writing our code in a different way from you and this is causing it not to trigger for you... |
|
|
Ok, it's not as bugged as i thought.. What happens is i type for example
I do get internal function hinting for stuff like
However i had to type out the whole @darken, no auto-completion whatsoever to help me get there, just like above for display: no drop-down coming up to propose to use inline, block.. I get suggestions for the first part of the property
but as soon as i type : it's gone, not even ctr+space will do anything.
So basically anything after the : is your on your own, no property auto-completion suggestions, no mix-in suggestions, no built in function suggestions. |
|
|
3.0 didn't fix any of this
|
|
|
3.0 was primarily focused on improving the compilation workflow and included only minor intellisense fixes. Now we've got it out the door, we hope to pick up the issues you've reported shortly, and we'll keep you informed! |
|