Check if PROGDIR: exists?

[AGS]

Hi,

how can I test if the PROGDIR: exists, but without using Lock()? It is not in the assigns list. The problem is, that when developing in AsmOne or Asm-pro, there is no PROGDIR:.

that's it
thanks
ags

[Cylon]

Well, your program is running, therefore the directory it is started from must exist ?!?

[AGS]

That's what we expect. And when it runs, then it works. I dunno what AsmOne/Pro are doing but when being inside and developing, there is no PROGDIR: available.

[AGS]

Ah, I just found the dos.library function GetProgramDir(). But it's buggy, says the doc.

[AGS]

btw: Where is the ENV: dir under OS 4+? I cant see it among the assigns anymore.

[thomas]

It's not a directory any more, it is a handler.

[AGS]

Thanks, and how can I check if ENV: handler existst w/o the Lock() function? I want no req showing up.

ps: Ah, maybe I should use LockDosList() with LDF_DEVICES!

[Leffmann]

This is one of many problems with ASM-One/ASM-Pro. Your program runs as a subroutine, which also means that if you started ASM-One from CLI, then you are a subroutine of a CLI process, and if you started from Workbench then you are a subroutine of a Workbench process, and you can't touch and work with the process and its data as if it were your own.

One work-around people often use is a simple equate, "FROM_ASMONE=1" or similar, and a set "if-else-endif" clauses, to handle the problematic cases differently when running from inside ASM-One.

The best solution in my opinion is to ditch ASM-One. If you want to do serious development, like you are doing with XoXo, then put ASM-One back in the toy-box where it belongs, and pick up a set of proper tools instead.

By the way, if you want a lock on your program directory then you can just use Process.pr_HomeDir.

[AGS]

I am not using AsmOne/Pro myself. I just got a mail that soemone has this problem with my GUI.

[thomas]

Originally Posted by AGS

Thanks, and how can I check if ENV: handler existst w/o the Lock() function? I want no req showing up.

You shouldn't lock it anyway. Only use GetEnv and SetEnv to access it.

To avoid a requester you can set pr_WindowPtr to -1.

To find ENV on the DOS list, just search for any type, not only LDF_ASSIGNS.

BTW, the same can happen on OS3, too, if the user has installed HappyEnv or similar.

[AGS]

BTW, the same can happen on OS3, too, if the user has installed HappyEnv or similar.

Ok, so it's good to implement a check.

[thomas]

What for a check? You need no check. Like I said, use GetEnv and SetEnv, nothing else, no check whatsoever. Do no expect ENV to be a file system.

[AGS]

No check, I meant it is good to search (check) for both ASSIGNS and DEVICES. What I am doing is not locking ENV: but just looking if it is there to avoid popping up requesters when doing the Get/SetEnv funcs.

[alkis]

Just disable requesters as Thomas said and re-enable them after you do your thing.