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



Thanks for that suggestion, Buck.
Curious though -- is the evolution of RDi so great between WDSc and today that many of the preferences from then don't fit today? I'm anticipating that some (or many?) preference labels may have different names now?
-- Michael
~~~~~~~~~~
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck
Calabro
Sent: Tuesday, July 15, 2014 3:42 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Porting workbench settings from WDSc 7.0.0.8 to
RDi 9.1?

On 7/15/2014 3:21 PM, Koester, Michael wrote:
Been using WDSc 7.0.0.8 since the Dark Ages, and finally it appears I
may be getting RDi 9.1.
Is it possible to export the workbench preferences and filters from
my old environment to the new?
Or will I need to rebuild (if I can remember how) everything?
Or is it unwise to want to import all the antiquity?

I dislike creating new workspaces so much that I've been known to edit
the raw properties files to correct anomalies in the workspace.

I created a brand new workspace for 9.1. I have been using Workspace
Mechanic to keep track of changes I make in Preferences and I like it
very much. Turn on the recorder, change the preference, save the
script. Now, every time I make a new workspace, Workspace Mechanic
prompts me to execute the scripts and update the settings -
automatically.
--buck


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.