Neil Riley scripsit:: > Dave > > in your example.... > > LRESPR win1_PTH_rext > PTH_ADD "win1_C68BIN_" > PTH_ADD "win1_QJUMP_" > PTH_ADD "win1_SYS_" > PROG_USE "PTH1_" > > Id expect DIR PTH1_ to show all objects in C68BIN , QJUMP & SYS. > > In my example i have two directories 48k and 128k ( and they are > directories off win1_) > > so ( and it seems the "" aren't really necessary ) > > 10 LRESPR rom1_pth_rext > 20 PTH_ADD "win1_48k_" > 30 PTH_ADD "win1_128k_" > 40 PROG_USE "PTH1_" > > Id expect dir pth1_ to show all objects in 48K and 128K but it only > shows > objects in 48K !?! swapping lines 20 and 30 shows only the objects in > directory > 128k ! > > Argh ! > > Neil > > PTH is not used like that.
PTH is good for your binaries' location. When it failed to find the binary in the first directory, it looks on the next, and so on. PROG_USE "PTH1_" is fine. DATA_USE "PTH1_" is dangerous: opening existing document is fine, but creating new file is a bad idea! Saving is also bad. PTH*_ devices are chained, so dir pth1_ show first directory, dir pth2_ the next... and so on. pth_list might be your friend too. _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
