| T O P I C R E V I E W |
| swinefeaster |
Posted - Apr 24 2007 : 5:18:34 PM
When creating new classes, I always have a problem with the stickiness of this command. I have it assigned to a hotkey, but whenever I press it nothing happens. I have to click on the same new function a few times to trick VAX to reparse the header and then it works.
Can't we do something like:
1. If symbol is known, execute command
2. If symbol is not known, reparse header, then check if known and execute command
This would be a huge improvement!
Keep up the good work guys.
|
| 3 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Apr 30 2007 : 08:05:56 AM
accord I am familiar with a similar effect, but so far I have not been able to reproduce it on demand. I am keeping an eye on this though, and hope to pin it down with time. |
| accord |
Posted - Apr 28 2007 : 5:31:43 PM
From build 1553, VAX reparsing times got better. Are you using the latest build? For me this has solved this problem.
Before 1553 I have ALWAYS reparsed my sources beforce I used a Create declaration or implamentation or move implementation to source command (from keyboard bindings)
I have written a script that saved, than reparsed my source and binded to Ctrl+S. So after a new function declaration I pressed Ctrl+S (save and reparse), then Ctrl+Q (my binding to create implementation)
But now, I leaved this script (now it tooks only one second for VAX to reparse my sources after every modification)
My bug regardless reparsing or not is that sometimes refactorings are NOT avaiable. After pressing left or right arrow, VAX recognises the symbol. Occours very rare, and there is no pattern to reproduce so far. |
| feline |
Posted - Apr 25 2007 : 05:27:17 AM
Someone else has already made the same request:
case=4568
For now you might try alt-o a couple of times, this should trigger a reparse of the header file, or you can manually reparse before triggering refactoring. |
|
|
