I know! It just came out but theres still pieces missing

[Ben Clark]

I have purchased both the PBWin 9 and PBCC 5 products.
As usual, PowerBasic has done a wonderfull job.
However, there is one thing still missing that I would kill to have and
probably wouldn't take much to add.
On the Code Finder window, it would be REALLY nice if it would
show the paramenters for the SUB and Functions.
That way, when you are working in one file, and you can't remeber
the function parms, you can just pop open the Code Finder, switch to
the file with the function, and there will be the parms for that function.
Almost as good as intellisence.

Anyone else think this would be usefull?

[Chris Holbrook]

On the Code Finder window, it would be REALLY nice if...

Agreed about the function headers.

Also, have you noticed whether both class methods and interface methods show up in Code Finder?

[Michael Mattias]

When you do submit your new feature suggestion to the official email address [email protected], include a sketch showing where on the screen you think this will fit.

I know how I'd do it, but it's your NFS so you have to figure it out yourself.

(Sheesh. Typical user. Wants to put ten pounds of stuff in a five-pound bag.)

[Gösta H. Lovgren-2]

On the Code Finder window, it would be REALLY nice if it would
show the paramenters for the SUB and Functions.
That way, when you are working in one file, and you can't remeber
the function parms, you can just pop open the Code Finder, switch to
the file with the function, and there will be the parms for that function.
Almost as good as intellisence.

Anyone else think this would be usefull?

Actually the Profile_Ordered_with_Variables.Inc (http://www.powerbasic.com/support/pb...ad.php?t=39112) has a list of Function/Subs with parameters. You could just create a Profile file and AltTab back and forth from your IDE and text editor.

[Cliff Nichols]

I am still thinking about the best idea to submit getting rid of "Forward Referencing" (or at least WARN if there is one") as I see it, "Forward Referencing" lets me use a function that has not been declared, and still lets me use it even if its after the function that uses it comes 1st in the compilers eye.

I consider it a small flashback to VB that I am trying to AVOID in the future

I like your idea as well, cause it would DEFINITELY help!!!!

Another one I am thinking of is "Duplicate Reference", but the error only shows you 1 reference, (would be nice to show both so you do not have to do a "File---->Search" to find out where else you did the same thing (but described differently) especially in large projects that the original code could have been written years ago, and you accidently did the same thing over again and not know it