| Re: [AD] Allegro 4.3 Settings/Conf API |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Allegro 4.3 Settings/Conf API
- From: Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx>
- Date: Thu, 17 Nov 2005 07:05:38 -0700
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=ZDQ/68re0raGGtpdtdFWIZZcqzdrehe8FxbyxKVpCAXUUUkniw0GRHp+uDhbULi0b89WMIM7wvV3caVIfXGD3jkB7KAWC/LG+sRc++5bJ+CjQ1u02qcg/7xvRn546HbPav6uqV17B4te36FBxAOBWHSU5uTwWCKwnw4PCj5jPdE=
On November 17, 2005 06:30 am, Vincent Penecherc'h wrote:
> > There's also the easier to use way of having unix style paths
> > and having Allegro translate and twiddle them (eg, like the #
>
> Sorry, just to make this clear: I was just referring to the part
> about creating paths from user given bits with that remark.
>
>
That is the general idea, but you still have to accept paths given from the
user, or a platform specific dialog perhaps?
>
>This is a separate issue from the canonical path list though.
In my view, they should be together. File handling is file handling.
--
Thomas Fjellstrom