RE: [WDSCI-L] Post your top 10 WDSC problems ...

[David McKnight <dmcknigh@xxxxxxxxxx>]

The compile menu action is grayed out before the save has been made on the
iSeries.  Once the operation is complete, it should become enabled again.
Save occurs on a thread and, within WDSC, whenever a menu is displayed, the
threaded activity is suspended.  So one possibility for the action staying
grayed out is that the menu keeps being displayed.  Michael, when you
encounter this problem, are you continually checking the menu?  I agree
that we should provide some indication of what's going on during the save.

The dirty indicator goes away immediately after saving indicating that the
editor contents have been saved to the cached file in the workspace.
However those changes still need to be propogated down to the host.


____________________________________
David McKnight
Phone:   905-413-3902 , T/L:  969-3902
Internet: dmcknigh@xxxxxxxxxx
Mail:       D1/643/8200/TOR
____________________________________



                                                                           
             Kelly Cookson                                                 
             <KCookson@DOTFOOD                                             
             S.com>                                                     To 
             Sent by:                  "'Websphere Development Studio      
             wdsci-l-bounces@m         Client for iSeries'"                
             idrange.com               <wdsci-l@xxxxxxxxxxxx>              
                                                                        cc 
                                                                           
             02/03/2004 08:51                                      Subject 
             AM                        RE: [WDSCI-L] Post your top 10 WDSC 
                                       problems ...                        
                                                                           
             Please respond to                                             
                 Websphere                                                 
                Development                                                
             Studio Client for                                             
                  iSeries                                                  
                                                                           
                                                                           




I have experienced the compile option being grayed out, too.  I usually get
around this by changing the cursor location within the LPEX source code.
Sometimes I have to change the location 2-3 times before the compile option
comes back.

Perhaps the cursor relocation had nothing to do with it (other than giving
me something to do while waiting for a save), but the save icon on the
toolbar grays out after it is clicked, giving the impression the member has
already been saved. Would the save icon on the toolbar gray out *before*
the
member has actually been saved on the iSeries? That is, does it gray out
upon sending the request to the iSeries, or does it gray upon receiving an
indication of a successful save?

Thanks,
Kelly



-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of
MichaelQuigley@xxxxxxxxxx
Sent: Monday, March 01, 2004 9:34 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Post your top 10 WDSC problems ...


     >>...(Oftentimes, the compile options are greyed out when editing a
     >> member.)
     >Your source member is either not in focus or it is in the act of
being
     > saved to the iSeries, most likely.
     The member is in focus.  I see what you're saying that the member
could
   be
     in the process of being saved.  But if the save is still in process, I
     would like the workbench to give me some indication of that.  All I
see
   is
     that I repeatedly click on the Compile menu option and my options are
     greyed out over and over again.  I guess this may just be one of the
     drawbacks of working in an asynchronous environment  I can kind of
     understand not wanting to wait for the save before I can do anything
   else,
     but currently the workbench gives a false impression that the source
is
     already safe on the 400.
   I don't think this is the problem.  I just saved a small source member
and
   for over three minutes I couldn't get the compile options.  Perhaps the
   workbench disables the options when it goes to save the member and isn't
   getting everything synched for when the member is saved?
_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.