Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!mcsun!ukc!mucs!p4.cs.man.ac.uk!gilbertd From: gilbertd@p4.cs.man.ac.uk (Dave Gilbert) Newsgroups: comp.sys.acorn Subject: possible bug in filer_opendir Keywords: bug filer_opendir expansion Message-ID: Date: 31 May 91 12:41:35 GMT Sender: news@cs.man.ac.uk Lines: 42 Someone has asked me to post the following article - here it is with his email address - please post replies to this group or mail him - not me. Simon Levitt Subject: Re. Filer_OpenDir I have a small problem with the Filer_OpenDir command. I have been trying for a while to get !TinyDirs to install directories on the icon bar from its startup... I have found out that you do this by passing in the directories to the application of start up e.g *!TinyDirs .... This seems to work at first, but when clicking on the icon on the Icon Bar the filer window just has the as it's title and not the full directory path... So I had the idea of giving !TinyDirs the full directory pathname when it is started. This seems to work until you click on the icon.... The Filer gives you an error Filing system not present or something simular. After a bit of investigation I found the problem It seems that using a system variable in File_OpenDir doesn't work properly, It doesn't seem to expand it! e.g Set Directory$Dir adfs::14_45_Fri.$ Filer_OpenDir .Directory won't work whereas Filer_OpenDir adfs::14_45_Fri.$.Directory does!!!! Am I doing something very stupid or is the problem in Filer_OpenDir command??? Cheers, Simon Levitt. -- ------------------------------------------------------------------------------- - Dave Gilbert - gilbertd@p4.cs.man.ac.uk - The MTBF of a piece of equipment - - G7FHJ@GB7NWP - is inversly proportional to its - ------------------------------------------- importance -