| T O P I C R E V I E W |
| fezztah |
Posted - Sep 12 2013 : 09:11:05 AM
Really frustrating problem when typing instances of variables in C++, it auto-completes with brackets as if this was a function or initialisation. This is v10.7.1940.0
|
| 5 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Sep 17 2013 : 9:11:49 PM
I actually mistook your variable for a function declaration myself on first reading the screen shot.
This change of format is just a workaround for now. This is on our list of things to fix, but unfortunately I don't currently have an estimate for when this will be done. |
| fezztah |
Posted - Sep 15 2013 : 05:48:33 AM
Ah, I see what you mean now.
C++11 initialisation looks like a bit like a function signature and that is confusing VAssist, but if you go back to traditional variable initialisation then there is no such confusion and everything works OK.
Definitely needs addressing, but that is a good work around for now. Thanks. |
| feline |
Posted - Sep 14 2013 : 11:10:14 AM
accord means to replace the declaration:
bool g_keyPressed(false)
with:
bool g_keyPressed = false;
I hope this is more clear. |
| fezztah |
Posted - Sep 14 2013 : 03:10:01 AM
That work around fails, you don't get the chance to type '=', it inserts the brackets immediately. This same behaviour occurs with instances of pointer variables too. The only option I could see is to turn off the option that auto-adds ( { [ completely. |
| accord |
Posted - Sep 13 2013 : 7:05:16 PM
I am seeing the same effect here. Thank you for the clear description.
case=60805
For now, a workaround would be to use the other form:
bool variable = false; |
