× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Regarding the name of the workspace:

Right click on the WDSC icon on your desktop
Choose Properties
Edit the "Target" field putting - at the end of your string - the
keyword -showlocation.
Make sure this keyword is AFTER anything else and outside anything that
may be sorrounded by ""
This will make the name of the wokspace show in your workspace title. I
am not sure but I think there is an option in Windows/Preference where
you can set up this, but this is a quick workaround.

Martin

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Bailey Paul
Sent: Thursday, September 20, 2007 4:30 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Close source members on close of
workspace or WDSC


Hi Rick,

Thanks for the advice. I've tried it and it doesn't seem to
do anything for my iSeries source members. If the source
member I had loaded in my previous session of WDSC changes
before I reload WDSC then I am completely unaware of any
changes until I try to save my new changes.
Then I have to decide which changes are more important or try
to merge both sets of changes somehow.

What I want to do is to have all my source members closed
automatically when I close WDSC. I thought this was possible,
previously. Has anyone seen this in WDSCv7?

Also, WDSC dev team - Please submit these as related change requests:
- Can we have the name of the workspace displayed somewhere
on screen? I can not find an option for this. The name of the
perspective and source member are shown in the task manager,
so why not the workspace?
- Can we have the connection name (used to load the source
member) displayed somewhere in the Remote Systems LPEX
Editor? Maybe in the tooltip, if not in the editor itself.


Best regards,
Paul

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Rick.Chevalier@xxxxxxxxxxxxxxx
Sent: 17 September 2007 14:03
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Close source members on close of
workspace or WDSC


Paul,

I think what you are looking for is the Refresh Workspace on
Startup preference. You can find it here:
window->Preferences->General->Startup
and Shutdown. If this preference is checked any changes made
to a source member outside of WDSC will be placed into the
workspace at startup. It takes a little longer to load WDSC though.

Rick

-----Original Message-----
From: wdsci-l-bounces+rick.chevalier=americredit.com@xxxxxxxxxxxx
[mailto:wdsci-l-bounces+rick.chevalier=americredit.com@midrang
e.com] On Behalf Of Bailey Paul
Sent: Monday, September 17, 2007 5:10 AM
To: Websphere Development Studio Client for iSeries
Subject: [WDSCI-L] Close source members on close of workspace or WDSC


Hi Group,

Is there a way of closing iSeries source members
automatically on exit from the workspace or WDSC? I thought
the preference "General->Editors->Close Editors
Automatically" would do the job but it doesn't.

The reason I ask is that I want to make sure that the locks
for source members are restored when the developer starts
working on them, but if you close WDSC and the iSeries locks
are removed, the cached source member is still available for
edit when WDSC is reopened. This can cause issues if source
has been changed outside of WDSC.

I saw a note from Don Yantzi in the archives, which is where
I got the idea for the preference I mentioned above, but it
doesn't close the source members.
(http://archive.midrange.com/wdsci-l/200409/msg00146.html)
Using this preference, source members are closed only when I
reach a set number of open members, and not when I close WDSC
or the workspace.

I am using WDSC v7.0.0.2i.

If there is no preference I am missing, and anybody knows how
to create a plugin to do this, then that would be an
acceptable solution.


Thanks,
Paul.

Privileged and Confidential. This e-mail, and any
attachments there to, is intended only for use by the
addressee(s) named herein and may contain privileged or
confidential information. If you have received this e-mail
in error, please notify me immediately by a return e-mail and
delete this e-mail. You are hereby notified that any
dissemination, distribution or copying of this e-mail and/or
any attachments thereto, is strictly prohibited.

--
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.



This message and any attachments contain information, which may be confidential or privileged. If you are not the intended recipient, please refrain from any disclosure, copying, distribution or use of this information. Please be aware that such actions are prohibited. If you have received this transmission in error, kindly notify us by e-mail to helpdesk@xxxxxxxxx We appreciate your cooperation.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].

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