Configuring Progress Compiler

[dolittle]

I have a few questions on the "Tool Configuration" option:

1. Is there a way to output to a dialog window.
2. Is there a way to automatically goto a line#
3. Is there a way to close the output window on certain conditions programmatically

[surround19]

I have a few questions on the "Tool Configuration" option:

1. Is there a way to output to a dialog window.
2. Is there a way to automatically goto a line#
3. Is there a way to close the output window on certain conditions programmatically

1. select "Create new File"
2. Use "Ctrl" + "G". Is this related to the "Tool Configuration"?
3. What do you do that it doesn't close automatically?

Chris

[dolittle]

Thanks, but that's not what I'm looking for.

When I select to run my progress compiler, I want to tell UltraEdit (automatically) perhaps as return codes. To go to a specific line# and close the output window.

[surround19]

Does this help?

Create user/project tools

[dolittle]

Yes, I have gone through this and setup everything up and it's compiling fine. I would like to take it a step further..... I don't UltraEdit supports what I want to do.

Let me explain what I'm trying to do.

When I compile my code by Pressing Ctrl-Shift-0, the text file is saved by UltraEdit and it calls the executable I have setup. I then usually am told I have a compile error at Line#45 for example. It would be great if UltraEdit took me directly to line $45 vs having to do a Ctrl-G blah blah. Just like any typical IDE like Visual Studio that takes you to the compile errors.

The closest I have to this in UltraEdit is by having outputting the name of the file and line-number in the output window and I then have to double click on it to take me to the line number on the file.

[danne]

Whoe... I know I'm digging up a really old thread here but I guess I missed it when it was posted, and incase someone else wonders...

Anyways, the solution is to call ultraedit from your check-syntax program. I've used this for years (since Zane Appel posted it his version... back in '97 this is modified to catch all errors/warnings). What you are interested in, as you already have a working program, is the os-command part.

Code: Select all

def var cErrors as char   no-undo.
def var ix      as int    no-undo.

compile value(session:param) save = no no-error.

output to "OE\chkSyn.txt".
if error-status:error or compiler:warning or compiler:error then
do:
    do ix = 1 to error-status:num-messages:
        cErrors = cErrors + error-status:get-message(ix) + "~n".
    end.

    put unformatted
        right-trim(cErrors,"~n").

    if compiler:error-row <> ? then
        os-command silent
            value(substi("start <path to>\Uedit32.exe &1/&2/&3",
                compiler:file-name,
                compiler:error-row,
                compiler:error-column)).
end.
else
    message
        "Syntax is correct".

output close.
quit.


I call this cmd-file from ultraedit: (I use output to listbox and capture all output, start dir is my ultraedit dir and oe is a subdir there)

Code: Select all

@echo off
path=C:\PROGRA~1\OPENED~1\bin;%path%
prowin32 -param "%1" -p .\OE\checkSyntax.p -pf .\OE\<db-info etc>.pf -ininame .\OE\<used inifile for project>.ini
type OE\chkSyn.txt
del OE\chkSyn.txt