comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » basic IDL_IDLBridge question
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: basic IDL_IDLBridge question [message #89303 is a reply to message #89302] Fri, 15 August 2014 00:25 Go to previous messageGo to previous message
Yngvar Larsen is currently offline  Yngvar Larsen
Messages: 134
Registered: January 2010
Senior Member
Assume that you have put all your initialization in a startup file, and issued

pref_set, 'IDL_STARTUP', '/path/to/your/startup/file', /commit

Then you can in the main process set up your bridges like this:

bridgearr = objarr(N)
for ii=0, N-1 do begin
bridgeArr[ii] = obj_new('idl_idlbridge', callback='your_callback_fn', output='your_log_file')
bridgeArr[ii]->execute, '@'+pref_get('IDL_STARTUP')
endfor

It is of course possible to adapt this to work with a custom startup file for bridges instead of using the IDL_STARTUP preference for the main process.

On Friday, 15 August 2014 08:28:28 UTC+2, Ken G wrote:
> An IDL_IDLBridge question, separate from all of the memory-leak headaches and whatnot. (I'm on Mac OSX 10.9.4, and IDL 8.3.2)
>
>
>
> I'd like the bridge object to be able to run code from my own procedure libraries. But since it launches without a startup file, my path and other variable definitions are not set up initially within the Bridge.
>
>
>
> So, what are the best ways that people handle this: i.e. to point an IDL_IDLBridge to my procedure libraries, in addition to the basic IDL functions?
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: error with struct expression
Next Topic: GPU implementation for Grey-Level-Co-occurance-Matrix & Haralick Matrix

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Thu Oct 09 22:42:49 PDT 2025

Total time taken to generate the page: 0.55868 seconds