SuperEdi

User: Guest

Search

Please use the
Bug Report Form
if you think you found a software defect.

Use the Contact Form
to send a personal message to Wolfgang.

RSS Feed RSS Feed

Other boards:
Juke
QBrowser
Raduga (English)
Song Requester

Macros in User Defined Tool not working?

Posted on: SuperEdi

From Message

tadas

2008-01-23 15:59:40

Macros in User Defined Tool not working?

I have tried to use $(FileDir) in User Defined Tools "Command" or "Start in folder" but it did not work.
Also is there a way to setup parser rule, so errors produced in OutputWindow could be clicked on (this applies when output tool or compiler produces some prefixes before any file with error).

Wolfgang Loch

2008-01-23 19:22:02

Re: Macros in User Defined Tool not working?

These macros are only valid in the Parameters and Start Folder fields, not in the Command field. See also: http://www.wolosoft.com/en/superedi/help/tools.html
I've just tried $(FileDir) in Start Folder and it worked fine for me.

The Command field should contain the full path name to the executable, without any parameters. You can use environment variables though.

Regarding parser rules, there are some pre-defined rules for Perl, Java, MSXML and Micorosft build tools. It's currently not possible to provide user-defined pattern. Which pattern would you need?

tadas

2008-01-23 20:16:38

Re: Macros in User Defined Tool not working?

I have to thank you for the great editor. Impressive!

1. Now about the macros:
Start Folder works now after I placed $(FileDir) into it and added extra space character after $(FileDir) . Works.
2. It would be nice to have ability to place macros in the Command field as well.
3. I am using VS 2005 MSBuild to perform a build and parser does not seem to work for MSBuild. Should it?
4. There is no keyboard shortcut to hide "Output Window". I am used to hitting "Esc" to hide it. But it could be any other easy one key shortcut.
5. Many editors support CTRL+W as close of active editor window (not just CTRL+F4). CTRL+F4 is just way too hard to reach with one hand...

Wolfgang Loch

2008-01-23 20:43:14

Re: Macros in User Defined Tool not working?

1. Which SuperEdi version do you use? I don't need a space in the start folder field.
2. Can you give an example where macros in the command field would be useful?
3. Can you give an example of the output?

tadas

2008-01-23 21:26:49

Re: Macros in User Defined Tool not working?

1. I am using 4.1.3 U. I think that is most recent one.

2. Example: $(FileDir)build.bat.
Sure it can be done by setting "Start Folder" to $(FileDir) and Command to build.bat . It is just nice to have feature if for some reason you would need "Start Folder" to be different from where Command is executing.

3. My current output is
"Csc: : ERROR LINE: D:\projects\etc.translator\src\xtraneng\edi\validator\axInfoItem.cs(76,78): The name 'segm' does not exist" (no quotes).

Having ability to define simple parser rule OR use build-in already existing rules would be ideal

4. Inability to close OutputWindow with simple shortcut becomes important when you make more than 10 builds per day. And if you are making >100 like me that really becomes important.

tadas

2008-01-23 21:35:54

Re: Macros in User Defined Tool not working?

5. This one is not major one but nice to have:
flag to Save All or current files before tool executes. You typed number of new code lines into the source file and forgot to press CTRL+S just before you run User Defined tool (compiler).

Post a reply to this message: