Re: Source Move

Hi Bill,

That is a bug in the caching code (there were a few related to how the 
lists of libraries, objects and members get built).  Some of them are 
fixed in 7.0 but there are a couple others we are planning to zap in a 7.0 
fix pack.  The workarounds are either refresh the source physical file (as 
Glenn suggested) or clear the cache (Windows > Preferences, then Remote 
Systems > iSeries > Cache) 

Don Yantzi
Technical Lead
WebSphere Development Studio Client for iSeries
IBM Toronto Lab





"Bill Barnes" <bbarnes@xxxxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
03/15/2007 10:42 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
<wdsci-l@xxxxxxxxxxxx>
cc

Subject
[WDSCI-L] Source Move








message: 8
date: Thu, 15 Mar 2007 08:38:19 -0500 (EST)
from: "Glenn Gundermann" <ggundermann@xxxxxx>
subject: Re: [WDSCI-L] Source Moving

Bill,

Have you tried clicking the source file name and then the refresh icon?

Glenn Gundermann
ggundermann@xxxxxx
(647) 272-3295

I have noticed that after I have worked on a particular source module

a

few times it has a tendency to migrate towards the top of the member
list.  Not always to the number one position but up none the less.

How

do I stop this from happening?  I know where it should be since I know
my alphabet.  Was this a request for this to happen from some new
Windows programmer that never learned their ABC's :-)?

Yes, I have and everything goes back where it belongs, my question is,
why did it move in the first place and is there something I can do to
stop it?