Re: Customizing WDSC

I know but this would make it so the copybook can be maintained from
INSIDE the program that uses it instead of opening another tab... 


Thanks,
Tommy Holden


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Jerry Adams
Sent: Friday, March 16, 2007 8:09 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Customizing WDSC

Tommy,

You can display the contents of the copybook by simply double-clicking 
it.  I don't use this often, but it is there.  Brings the copybook up in

a separate window, though, not in the current source member's window.


        * Jerry C. Adams
*IBM System i5/iSeries Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
        615.995.7024
fax
        615.995.1201
email
        jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



Holden Tommy wrote:

Got a small request.  Can you make it where we can expand copybooks
inside the opened source? Maybe a little plus sign to expand/collapse?
That would rock! 


Thanks,
Tommy Holden


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx

[mailto:wdsci-l-bounces@xxxxxxxxxxxx]

On Behalf Of Violaine Batthish
Sent: Thursday, March 15, 2007 4:35 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Customizing WDSC

Hey Bob,

Yes, I agree.
We already have a requirement on our list to indicate when there are

no

errors retrieved into the error list, and when there are errors, but
they
have all been filtered out.

thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab



wdsci-l-bounces@xxxxxxxxxxxx wrote on 03/15/2007 05:23:12 PM:

  

Violaine,
I have WDSC 7.

    

As for compile feedback, any generated errors appear in the Error
        

List
view
  

once compile completes.


True enough--the point is "any errors" if there are none, there's no
    

visual
  

feedback the compile finished. I have to click over to the joblog tab
    

scroll
  

down to the bottom and see if I got a good completion message.
Since the keyboard is apparently locked while compiling (not sure why
    

that is,
  

but okay) then it should popup a window or perhaps a message in the
    

error
log
  

view with "no errors detected and the date/time stamp.

    

I believe if you check the archives, there are extensive

discussions

on
how
  

to override/define key behaviour in LPEX.

I'll do that. Thanks!

-Bob Cozzi