Cannot resolve QUERY_JPEG [message #52550] |
Tue, 13 February 2007 11:05  |
biophys
Messages: 68 Registered: July 2004
|
Member |
|
|
Hi,
I have a .sav file from my colleague that works fine on linux box but
fails on windows machine. It gives out some warning saying QUERY_JPEG
not resolved. The guy is no longer maintaining the code so I looked up
his original code and couldn't figure out where the hell the
QUERY_JPEG is getting called. How can I force it to resolve
QUERY_JPEG? I tried the keyword resolve_function= 'QUERY_JPEG' and it
did not work. What else do you guys suggest to get this straight?
thanks a lot!
bp
|
|
|
Re: Cannot resolve QUERY_JPEG [message #52688 is a reply to message #52550] |
Wed, 14 February 2007 03:32  |
biophys
Messages: 68 Registered: July 2004
|
Member |
|
|
nevermind, pref_set fixed the problem.
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;;;;;;;;
idl> pref_set, 'IDL_DLM_PATH', 'F:\my\DLM\path;<IDL_DEFAULT>',/commit
bp
On Feb 14, 3:00 am, "biophys" <biop...@gmail.com> wrote:
> It seems that something is broken under my windows machine. I tested
> the following routine and it works fine under linux and other windows
> machines. My windows idl just can not load DLM of jpeg from within
> virtual machine. Other dlms like PNG etc all load fine. JPEG loads
> fine in normal idlde session. So what could be wrong here? I
> reinstalled idl and it doesn't help. Any hidden variables I can tweak?
> Any suggestions?
>
> Thanks,
> bp
>
> ;;;;;;;;;;;;;;;;;;;;;;
> ;testing query_jpeg
> pro test_query
> print, query_jpeg('export.jpg')
> end
>
> idl>.compile test_query
> idl>resolve_all
> idl>save,/routines,filename='test_query.sav'
>
> On Feb 13, 12:39 pm, FĂ–LDY Lajos <f...@rmki.kfki.hu> wrote:
>
>> On Tue, 13 Feb 2007, biophys wrote:
>>> Hi,
>
>>> I have a .sav file from my colleague that works fine on linux box but
>>> fails on windows machine. It gives out some warning saying QUERY_JPEG
>>> not resolved. The guy is no longer maintaining the code so I looked up
>>> his original code and couldn't figure out where the hell the
>>> QUERY_JPEG is getting called.
>
>> add a fake QUERY_JPEG function:
>
>> ; ------------------
>> function QUERY_JPEG
>> print, unknown
>> return, 0
>> end
>> ; ------------------
>
>> the error message shows which routine calls it.
>
>> regards,
>> lajos
|
|
|