Hyperion Entertainment Message Boards

GetVar() allows you to specify a device spec in front of the variable to specify which device root. ie: "ENVARC:foobar".
The default without specifying anything is of course, "ENV:". I'll update the autodocs.

NotifyVar() works simply by adding hook structure nodes to a list. When an environmental function is called that modifies a variable, like SetVar() or DeleteVar(), the variable with the matching name has it's hook function called, and you do what you need to in there. That's it, nice and simple and ...

Has enyone an explanation for such strange thing? Looking at your log, I can see a possible race problem which the priority change could affect. You will notice that line 142 Open()'s the file in "NEW" mode, which implies an EXCLUSIVE_LOCK, but immediately afterwards on line 143 a SHARED_...

Hi using in DateTime.docky to launch an external program (SYS:Prefs/Time) when I click on Time prefs USE|SAVE I get a requester 'Could not open input file "ENV:Sys/time.prefs".' Any ideas why I get such requester? TIA Is it a requester, or a text message in the console window you opened. ...

Firstly it's; AllocDosObject(DOS_VOLUMELIST, ) [not ADO_DEVICELIST] So, for this reply, I will assume you are actually using; DOS_VOLUMELIST with the tag; ADO_Type set to LDF_DEVICES. If this is the case, you may wish to filter the devices returned first by using IDOS->IsFileSystem(), that will at l...

char buf[512];
-> return buf;

'buf' is an auto variable, it disappears when you leave the function.

There are certain characters used in pattern matching, namely the ones found in the autodoc for DOS/ParsePattern(). None of which are specifically "forbidden" in filesystem object names, but their use will eventually cause you a world of hurt. Here are the current pattern matching tokens: ...

Besides the previous 40 byte display buffer limitation, the displayed argument string will also be truncted
at the first ascii character less than value 0x20 (char 32). That's all.

I've just rechecked and Snoopy's argument buffer was 39 characters long, so the string was truncated for display.
I've just fixed it for the next update.

There is no supplied "devs:Mountlist" anymore, even though the c:mount command will still look for it
if the particular device info is not found in the "devs:DosDrivers" directory where individual mount files
are now the standard.