Home › forums › Prolint

Prolint results screen - Open sourcefile in Editor

Wed, 2007-06-13 11:00 — rapier

On the 'Prolint results screen' there is a button labelled 'Open sourcefile in Editor'.

I run Prolint from PRO*Tools and use the 'Lint Active AB' button.

When I click the 'Open sourcefile in Editor' button nothing happens. Is something supposed to happen?


‹ tablename rule reports unqualified fields in FIELDS() new rule help ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Wed, 2007-06-13 21:29 — jurjen
jurjen's picture

Re: Prolint results screen - Open sourcefile in Editor

Hi,

What was supposed to happen, is that the sourcefile is opened in an external editor and the cursor is positioned to the line where the problem is. But before this can happen Prolint needs to learn which editor you are using and where that executable is installed. If nothing happens it probably means that the default setting, which is actually an example setting, is not right for your situation and you may need to change it.
There is an example and some information in the documentation: look for "file exteditor.cfg" on page http://www.oehive.org/node/236

But frankly, since the file is already open in the Appbuilder I think it is a bad idea to also open the file in an external editor. Instead it would be much better, in this situation, if Prolint could ask Appbuider to switch to the offending code section and put the cursor on the right spot, but I never figured out how to do that.

Hope this helps,
Jurjen.


Fri, 2007-06-15 09:26 — rapier

Re: Prolint results screen - Open sourcefile in Editor

Thanks,
I now have it configured to open in Ultra Edit.

I can use that to see where the problem is so I can find it in AppBuilder.

Is there any way to get the ProLint results window to show me which PROCEDURE or FUNCTION contains the problem line of code?


Sat, 2007-06-16 21:19 — jurjen
jurjen's picture

Re: Prolint results screen - Open sourcefile in Editor

> Is there any way to get the ProLint results window to show me which PROCEDURE or FUNCTION contains the problem line of code?

No I am afraid not. It would cost a horrible lot of programming to display the function/procedure/method/trigger name. Determining the context is one thing, but it would also have to be passed as a new parameter in every call to "PublishResult" and there are so many calls to that procedure that you would have to edit almost every sourcefile in Prolint.

Since filename and linenumber are known, it would probably be more productive to learn how to move the cursor in the appbuilder section editor to that specific location.