kicad-developers team mailing list archive

[easyw <easyw@xxxxxxxxxxxx>]

Hi Cirilo,

please consider to let users to use also $ENVAR
with the new 3D refactor $ENVAR variables (ie.e KIPRJMOD) are still 
interpreted but cannot edited

if you want to make a change to a model name still including i.e. 
KIPRJMOD, the pcbnew dialog will reject it, forcing the user to drop $ENVAR
Error message: Invalid filename

Maurice

On 12/04/2016 08.18, Cirilo Bernardo wrote:
> Hi folks,
>
>   The current behavior of the 3D filename resolver is to use
> an absolute path in instances where a specified path is
> not a descendant of a path within the aliased paths list
> (that is, the filename cannot be shortened using an existing
> alias). This decision was originally made to avoid ambiguous
> relative paths such as "../../some/path" (what is it
> relative to?).  The obvious down side of course is that
> absolute paths are not portable and this scheme would
> be a nuisance to people who want to share their work
> somehow.  Since a number of people seem to be reliant
> on using the "../" form of relative path to share their work,
> I'd like to know people's opinions on using such relative
> paths. If such relative paths are preferred to absolute
> paths then I can make changes to the code such that
> the resolver will assign a path relative to the Current
> Project Directory rather than an absolute path in cases
> where the file path cannot be shortened via the use of
> an alias.
>
>
> - Cirilo
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp