Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Feature Requests
 Remove static code analysis information from tips

You must be registered to post a reply.
Click here to register.

Screensize:
UserName:
Password:
Format: BoldItalicizeUnderlineStrikethrough Align leftCenterAlign right Insert horizontal ruleUpload and insert imageInsert hyperlinkInsert email addressInsert codeInsert quoted textInsert listInsert Emoji
   
Message:

Forum code is on.
Html is off.

 
Check to subscribe to this topic.
   

T O P I C    R E V I E W
spectecjr Posted - Nov 15 2008 : 9:56:26 PM
Currently, when I start filling out a call to say, ReadFile, I get a tip like this:

WINBASEAPI BOOL WINAPI ReadFile( __in HANDLE hFile,
    __out_bcount_part_opt(nNumberOfBytesToRead, *lpNumberOfBytesRead) __out_data_source(FILE) LPVOID lpBuffer,
    __in        DWORD nNumberOfBytesToRead,
    __out_opt   LPDWORD lpNumberOfBytesRead,
    __inout_opt LPOVERLAPPED lpOverlapped
    );


... is there any way that you could give me the option to cull the static analysis markup so that I get something more like this?

WINBASEAPI BOOL WINAPI ReadFile( HANDLE hFile, LPVOID lpBuffer, DWORD nNumberOfBytesToRead, LPDWORD lpNumberOfBytesRead, LPOVERLAPPED lpOverlapped);


... or otherwise reformat it? For example, for optional parameters it might be cool to see this:

WINBASEAPI BOOL WINAPI ReadFile( HANDLE hFile, LPVOID lpBuffer, DWORD nNumberOfBytesToRead, LPDWORD lpNumberOfBytesRead, LPOVERLAPPED lpOverlapped);


Additionally, any kind of support you could add for adding those markup strings would also be awesome.
2   L A T E S T    R E P L I E S    (Newest First)
spectecjr Posted - Nov 28 2008 : 6:45:07 PM
I guess the most logical way would be to allow the user to define macros to not show.

Parse them like regular macro definitions, and just eliminate them if they show up.

That way it's future proof.
feline Posted - Nov 18 2008 : 4:07:53 PM
We don't have any current plans to do this, but I do see the appeal.

My main concern here is how do we define what to exclude and what to include? To start with a simple case, what about "const"? You can add "const" twice to a single parameter, but I would consider that important to see in the tooltip.

With some of the more "creative" code I see sometimes it is difficult for our parser to tell where one parameter stops and the next one starts. People often define their own macro's and use them in function declarations, so we would not know if we should include or exclude them.

© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000