Re: IDL 8.0 onwards: can I always use the same workspace? [message #91048 is a reply to message #91047] |
Thu, 28 May 2015 00:21   |
Helder Marchetto
Messages: 520 Registered: November 2011
|
Senior Member |
|
|
On Thursday, May 28, 2015 at 8:44:14 AM UTC+2, Mari Liza wrote:
> On Wednesday, May 27, 2015 at 3:08:09 PM UTC+3, David Fanning wrote:
>> Mari Liza writes:
>>
>>> Do you know if it is possible to always use the same workspace for ALL IDL instances? for all loadings of IDL? so that IDL does not prompt me all the time for a new workspace?
>>
>> Uh, as far as I know, that's what the rest of us always do.
>>
>> What's amazing to me is how you ever got into a situation where you are
>> using dozens of them. I must be having a failure of the imagination,
>> because I can't even come up with a plausible explanation for how such a
>> thing could happen. :-(
>>
>> Cheers,
>>
>> David
>> --
>> David Fanning, Ph.D.
>> Fanning Software Consulting, Inc.
>> Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
>> Sepore ma de ni thue. ("Perhaps thou speakest truth.")
>
>
> Dear David,
>
> Do you mean to tell me that you are able to simultaneously load two, three, four different IDL 8.0 onwards in WINDOWS and not have IDL ask you for a new workspace each time?
>
> PLEASE tell me how to set this up, I have tried everything, unclicked all sorts of "refresh workspace at start-up", "prompt for workspace at start-up", I have asked IDL to keep in memory 30 different workspaces, but nothing works. If IDL is running once, then from the second instance onwards it asks for a new workspace.
>
> This includes running save files simultaneously.
>
> Thank you!
> MariLiza
Hi,
I'll jump in without knowing exactly what David meant, so I'll speak for myself.
*why* do you need to start more that one IDLDE session?
So here is my way of doing things. The idlde (development environment or simply DE) is made to develop code. And to develop code, one DE with one workspace is more than enough (at least for me!). If you have more persons developing code together then they will be using different PCs and you will need to manage revison/version control.
To *run* code you have *also* other options:
1) the development environment of course
2) the idl_idlbridge to run more that one process at the same time (see http://www.exelisvis.com/docs/IDL_IDLBridge.html)
3) the idl virtual machine or VM can run .sav files ( http://www.exelisvis.com/docs/StartingVirtualMachineApplicat ion.html)
4) the command prompt in windows is also another option and does not require a workspace and you can run multiple instances.
That said, here is how I use the above. I normally write code in the DE, test it or execute it within the DE and execute the final product (.sav) in the VM. In the VM I can run as many processes as I want. The idl_idlbridge is a little bit more tricky and there are loads of posts describing what it is useful and not useful for.
Hope it helps.
Cheers,
Helder
|
|
|