Re: No *ESCAPE message on wrong compile command

Of course that is a good point and that is why some views, such as the
"Console" have buttons as "Show Console When Standard Out Changes".

Edmund, the problem with the message dialog is not that important for
me. So I do not mind keeping it the way it is and I try to get used to
the "Commands Log" or switch to batch compile.

Thomas.

Am 28.02.2016 um 14:28 schrieb Stuart Rowe:

Edmund,

The message box might be obtrusive and annoying.

I don't think it would be any more annoying or obtrusive than opening (even
if it is closed) and displaying (even if it is minimized) the error list
after EVERY COMPILE, good OR bad. I've been fighting that one for years
now. It steals focus away from where I am typing -- really annoying. I
guess that "the Eclipse way" though.

Stu



On Sat, Feb 27, 2016 at 1:23 PM, Tools/400 <thomas.raddatz-a9TbBav64t4b1SvskN2V4Q@xxxxxxxxxxxxxxxx>
wrote:

Edmund,

Most of the time I compile objects interactively and hence I expected to
get a message dialog for a failing command much the same as on a command
line. For batch compiles I can use the iSphere Message Monitor.

But it might be worth to improve RDi to either display the "Error List"
or the "Commands Log" depending on the availability of *EVENTF entries.

Thomas.

Am 26.02.2016 um 18:43 schrieb Edmund Reinhardt:

We don't currently have an option to do that.
Would making the Commands Log view visible if a command (that does not

have

*EVENTF) fails be sufficient.
The message box might be obtrusive and annoying.




From: Tools/400 <thomas.raddatz-a9TbBav64t4b1SvskN2V4Q-XMD5yJDbdMReXY1tMh2IBg@xxxxxxxxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries
<public-wdsci-l-Zwy7GipZuJhWk0Htik3J/w@xxxxxxxxxxxxxxx>
Date: 26/02/2016 11:36 AM
Subject: Re: [WDSCI-L] No *ESCAPE message on wrong compile command
Sent by: "WDSCI-L" <wdsci-l-bounces-Zwy7GipZuJhWk0Htik3J/

w@xxxxxxxxxxxxxxxx>

Hi Vern,

The problem has nothing to do with the *EVENTF option. There are lots of
commands that do not have that option and I wonder how to get noticed by
RDi when such a command fails.

Today, I had a problem with a command of our change management system
that sent an *ESCAPE message, which was silently ignored by RDi. Then I
did additional tests and tried to compile a RPGLE source member with
CRTFOODCMD (which does not exist) and CRTTBL (which should not
understand a RPGLE source).

Guess what? Nothing happened what I tried to compile the module from an
RSE source member filter. That is really bad, when you are in a hurry
and you think that it compiled just fine.

At least I would like to see an option to enable a popup message box

when:

* a command, that does not have specified *EVENTF, failed
* there is a typo in a custom compile command

The popup is not really necessary (maybe even annoying) when the command
created *EVENTF information.

Thomas.

Am 26.02.2016 um 16:34 schrieb Vernon Hamberg:

*EVENTF option

--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L-Zwy7GipZuJhWk0Htik3J/w@xxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request-Zwy7GipZuJhWk0Htik3J/w@xxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.

--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L-Zwy7GipZuJhWk0Htik3J/w@xxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request-Zwy7GipZuJhWk0Htik3J/w@xxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.