Message-Id: Comments: Authenticated sender is From: "Salvador Eduardo Tropea (SET)" Organization: INTI To: Eli Zaretskii , djgpp AT delorie DOT com Date: Tue, 5 May 1998 09:25:48 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: fixpath problem in Novell drives. References: In-reply-to: Precedence: bulk Eli Zaretskii wrote: > On Mon, 4 May 1998, Salvador Eduardo Tropea (SET) wrote: > > > > I believe that if you use `stat' this way, you won't need to mess with > > > `_truename' and `_fixpath' at all. > > > > Ok, I'll see if I can use it, but the user will have a fake name in > > the top of the window. > > Sorry, I don't understand this. Which fake name are you talking > about? Suppose the user enters it in the save window: c:\long_name.txtt and I'm in a non LFN system, when I pass it to fopen it works OK and creates a file long_nam.txt. The user sees in the window caption the fake name (the one he specified). It produced a bad side effect in the editor: If the user then opens long_nam.txt the editor is fooled and opens it (is dangerous in my editor open the same file twice). To avoid it I was using first _truename getting: C:\LONG_NAM.TXT and to avoid the ugly dosish name I was passing it to fixpath, getting c:/long_nam.txt. In this way: 1) The user have the real name of the file as name for the window. 2) The user can't easilly fool the editor. Currently I'm thinking about having 2 names, one the name entered by the user and the second name the truename. SET ------------------------------------ 0 -------------------------------- Visit my home page: http://set-soft.home.ml.org/ or http://www.geocities.com/SiliconValley/Vista/6552/ Salvador Eduardo Tropea (SET). (Electronics Engineer) Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org ICQ: 2951574 Address: Curapaligue 2124, Caseros, 3 de Febrero Buenos Aires, (1678), ARGENTINA TE: +(541) 759 0013