Whole Tomato Software Forums - Changing preference of autocomplete function names

Whole Tomato Software Forums

User name:	Password:
Save Password
Forgot your password?

All Forums

Visual Assist

Technical Support

Changing preference of autocomplete function names

New Topic

Reply to Topic

Printer Friendly

Author

Topic

JoTo
New Member

3 Posts

Posted - Jun 11 2007 : 06:59:02 AM

Hi Forum,

i am using:
VA_X.dll file version 10.3.1555.0 built 2007.04.26
VAOpsWin.dll version 1.3.2.0
VATE.dll version 1.0.5.4
DevEnv.exe version 8.0.50727.762
msenv.dll version 8.0.50727.762
Comctl32.dll version 6.0.2900.2982
Windows XP 5.1 Build 2600 Service Pack 2
wxWidgets 2.7.3

Problem:
I use C/C++ in conjunction with the wxWidgets class framework. When using the class wxString and the member function "printf" (that i use veeeery often) i always get from Visual Assist suggested and autocompleted the "printfV" method (that also exists in this class for an variable argument list version of printf).

But most of the time i don't want to use the printfV method. In 99% of the time i want use printf. But VA insists to autocomplete printfV instead of printf. Then i often oversee this and get compiling errors that i have to correct then or if i notice it immediately i have to move the caret back manually and delete the unwanted V character.

Thats very annoying. I cant find a way to "teach" VA to autocomplete printf in preference instead of printfV.

Can s.o. point me in the right direction to solve this? Any hint appreciated.

TIA
Joerg

feline
Whole Tomato Software

United Kingdom
19014 Posts

Posted - Jun 11 2007 : 07:07:13 AM

Can you try adding an autotext entry? I would suggest something like this:

shortcut = pr
text = printf("$end$");

This way when you type the shortcut the suggestion will come from autotext, which takes priority over other items, and you also get any extra text you want entered along with the function name.

zen is the art of being at one with the two'ness

JoTo
New Member

3 Posts

Posted - Jun 12 2007 : 06:19:18 AM

Dear feline,

tried it.

It works very well if i type "pri" now without any context (standalone) in the editor.

But if i use an instance of wxString class in front of it (e.g. wxString mystring; mystring.pri) it wont offer me my new autotext Printf entry. It solely offer again only the PrintfV class member of wxString class.

Dunno if there is a problem in wxWidgets that only the PrintfV method of wxString is suggested and not the, definetely there, Printf method.

Any other hint, suggestion? All is very appreciated.

TIA again
Joerg

feline
Whole Tomato Software

United Kingdom
19014 Posts

Posted - Jun 12 2007 : 08:51:59 AM

*ah* I did not fully understand the problem. I have just installed wxWidgets 2.8.0 and I am seeing the same problem. Jumping to:

C:\\wxWidgets-2.8.0\\include\\wx\\string.h

line 1149 the problem is the macro after the function:

  int Printf(const wxChar *pszFormat, ...) ATTRIBUTE_PRINTF_2;

I have just tried making VA ignore this macro, but it is not working in VA 1557. The easiest solution is to turn on:

VA Options -> Advanced -> listboxes -> Get content from default Intellisense

alternatively you could edit this header and remove this macro.

Macro's after functions confusing our parser is a known problem:

case=4589

zen is the art of being at one with the two'ness

JoTo
New Member

3 Posts

Posted - Jun 13 2007 : 09:35:04 AM

Dear feline,

thank you so much! Enabling "Get content from default intellisense" solved my problem immediately.

Visual Assist is so great! Can't understand how i could live so long without it!

CU
Joerg

support
Whole Tomato Software

5566 Posts

Posted - Oct 29 2007 : 02:35:08 AM

case=4589 is fixed in Build 1614

Topic

New Topic

Reply to Topic

Printer Friendly

Snitz Forums 2000