kicad-developers team mailing list archive

[Nick Østergaard <oe.nick@xxxxxxxxx>]

No, that is not a good design IMHO. You should be able to use every
option in a single project if you wish to. But I like to be explicit.

A suggestion I have have somewhere before is to use theese variables
in the path. So i you want ti projecet relaive use KIPRJMOD if you
want "global" models, use the KISYS3DMOD variable, and make it easy
for the user to enter even with browsing.

2015-09-27 18:48 GMT+02:00 Thor-Arne <lp@xxxxxxxxxxxxx>:
> I think the absolute adressing should be good enough for those special
> cases.
> Special cases shouldn't affect the "normal" cases.
>
> -----Original Message----- From: Mark Roszko
> Sent: Sunday, September 27, 2015 6:38 PM
> To: Thor-Arne
> Cc: KiCad Developer mail-list
>
> Subject: Re: [Kicad-developers] 3D model relative path dialog
>
> I am advocating only for people who don't want to globalize their
> models that might be super specific. If I have a custom extruded
> heatsink model(because custom heatsinks are dirtcheap) that is
> literally only made for one board, why would I
> want to put that in the global folder?
>
> On Sun, Sep 27, 2015 at 12:32 PM, Thor-Arne <lp@xxxxxxxxxxxxx> wrote:
>>
>> Relative to board file is a bad idea, it will require 3D models to be
>> duplicated for each project.
>> Perhaps this should be handeled by the File->Export->VRML (not that I've
>> tried that one).
>>
>> And, yes. Please apply this patch. ;)
>>
>> -----Original Message----- From: Mark Roszko
>> Sent: Sunday, September 27, 2015 6:19 PM
>> To: Simon Wells
>> Cc: KiCad Developers
>> Subject: Re: [Kicad-developers] 3D model relative path dialog
>>
>>
>> Relative to the board file seems like a better idea btw. In case you
>> want to package 3d models with a PCB when distributing the source.
>>
>> On Sun, Sep 27, 2015 at 7:46 AM, Simon Wells <simonrwells@xxxxxxxxx>
>> wrote:
>>>
>>>
>>> When you add a 3d model for a footprint
>>>
>>> If the model file is inside the KISYS3DMOD directory then it is
>>> automatically made relative path
>>> If the model file is outside the KISYS3DMOD directory then you get a
>>> dialog
>>> as to whether it should
>>> be relative or not,
>>>
>>> If the model file is not in the KISYS3DMOD directory it seems like a bad
>>> idea to make the model
>>> have a relative path because if you move either the KISYS3DMOD directory
>>> or
>>> the model it
>>> requires changing the path, whereas if its absolute then you only need to
>>> update the path if you
>>> move the model file.
>>>
>>> I have created a branch with a patch to remove the dialog and if theres
>>> consensus then i will submit
>>> a merge request with it. (the branch is lp:~xzcvczx/kicad/relpath-dialog)
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>
>>
>>
>> --
>> Mark
>>
>> _______________________________________________
>> 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
>>
>> _______________________________________________
>> 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
>
>
>
>
> --
> Mark
>
> _______________________________________________
> 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