| T O P I C R E V I E W |
| tom_seddon |
Posted - Feb 22 2006 : 12:54:25 PM
It would be cool if FSIW, having done the "F" bit, could highlight the text of the symbol you looked for. This would then enable a swift Ctrl+F3, Alt+O, F3 to find (probably) the definition, since FSIW only ever seems to give you the declaration.
|
| 5 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Feb 28 2006 : 3:08:14 PM
to be honest i picked up column 1 alt-g from support, it was not something i naturally tried either *shrug* |
| tom_seddon |
Posted - Feb 28 2006 : 11:24:24 AM
I don't see my suggestion working with OFIW... what would it do?! (But to take your question, in FSIW it would highlight the text you selected from the search string. So if I were to type in, say, "sionte" to find "compressiontest", then pressed enter, it would highlight "compressiontest". The text I type in is just whatever I need to get the right result, and can be discarded.)
However your "alt+g in column 1" suggestion indeed works fine -- I never thought to try it. (I'll leave the reader to draw the obvious conclusion.) Thanks!
|
| feline |
Posted - Feb 23 2006 : 09:54:06 AM
at the risk of being unhelpful, how do you see this working with the following search string:
path -moc manual result
which is something i do a lot in OFIW.
this is matching all entries with the pieces "path", "manual" and "result" in them, in any order, and not having the string "moc".
in this case i was after the file "mtQtPatientPathManualResult.cpp"
i know this is files, but i do the same mangled searches in FSIW, it is just this was a recent and good example.
turning to alt-g and FSIW i have just been using this. jump to a function with FSIW and press alt-g imidiately, without moving the caret from column number 1 takes me to the function definiton.
it could be that what you want already exists  |
| tom_seddon |
Posted - Feb 22 2006 : 3:47:34 PM
Right, the Alt+G suggestion is a good 'un, and sure enough it seems to work. So I will upgrade/downgrade my suggestion to this: that the cursor position be on the text you looked for. Currently it's at column 1 of the line. My only complaint, really, is having to move the cursor :)
(By "the text you looked for", I don't mean what you typed in, but the actual text, out of the listbox, Visual Assist tried to find in your program.) |
| feline |
Posted - Feb 22 2006 : 2:01:07 PM
i can see a couple of possible problems with this. firstly when i use FSIW and OFIW i very rarely type complete file or symbol names. instead i type parts of names, often with spaces between the parts.
the second problem is that if the dialog is highlighting text if you press the wrong key you instantly edit the code, replacing the highlighted text.
i am making the assumption that you are focusing on functions when you say this. are you aware that if you simply move the caret into the function name you can press alt-g to take you to the definition?
i am wondering if there is a better way of achieving the effect you are after. |
|
|
