I have been trying to do more and more of my development in WDSCi and it is going well. I really like 6.0 but I have to admit I haven't taken time to learn all the features yet, so bear with me if I missed something obvious here.
I just started to compile programs from WDSCi 6.0 (I used to just run 
compiles from the command line).  Is it just me or is the setting of 
library lists a clunky procedure? I set the library list, laboriously 
moving between mouse clicks and keying to get the list built in RSE.  At 
that point I was happily compiling away.  I ended my WDSCi session, shut 
down my notebook headed home, fired it up there and started WDSCi again 
and on my next compile got a bunch of errors indicating that stuff was 
missing from the library list.  The list in RSE looked fine, until I hit 
refresh, and then my libraries disappeared from the list.  So I added 
them all back in. Kind of a pain.
So here is the question/rant:  Is it possible to retain the library list 
as a value and then load it during the startup of RSE?  What I'd love to 
have is a way to store a bunch of library lists as "loadable" values 
when I am in RSE.  Yes, I know that I could write a CL to do this and 
can call it, but these libraries and names can be pretty fluid and it 
would be great save them and switch between them while in RSE. That 
would be an "optimal" solution.
Barring that, is there a way to access the library list in a view that 
doesn't require 1 by 1 entry?  Similar to the edtlibl command ?  
Bringing up a screen that would allow multiple libraries to be added 
would be great.
Perhaps these features are already there?  Perhaps my newbie eyes are 
just missing something?
Outside of CL programs and job descriptions, how are others handling 
library lists in WDSCi?
Thanks.

Pete Helgren


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact copyright@midrange.com.

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.