the use of the project file is inconsistent

[sugeng anto]

I created the project : usbasp

These would have 2 versions of sch : SMD (usbasp_2_0_0.sch) and PDIP version (usbasp_1_0_0.sch)
All library I put in the project file : usbasp.pro to share to all schematic ( I have own lib folder).

It also has several version of pcb which also I put the library setting on usbasp.pro to share to all board.

but why both sch and pcbnew ask for another project file (usbasp_1_0_0.pro and usbasp_2_0_0.pro)? Is that should use the same project file?

The bad things is cvpcb which forced to create usb_1_0_0.pro and don't even ask for it by default. I must open the net file manually from empty cvpcb to force it to save into new project file.

the footprint filter often failed. Maybe it is because I use custom library which is not loaded because it think of different project file.

kicad BZR 3811 compiled using mingw32 gcc 4.7.0, wxwidget 2.9.3

[Joonas Reunamo (joonas-reunamo)]

Hello!

This is a major problem in Kicad in my opinion. Project .pro cannot contain several schematic .sch files correctly. New schematic files are easy to add with "save current sheet as..." and they appear in project tree, but added libraries are saved in .pro and new schematic will need a new .pro which also appears in the project tree. Not only ugly, but confusing and useless as well.

Why there is r .pro if every schematic needs a separate .pro anyway? Why not to add the information directly to .sch file then, at least copy-paste would work?

In my opinion project should hold several schematic files and a general preferences of a full project. Project isn't always just a one .sch and one .brd. Often there is multiple boards needed within one project like RX and TX sides.

[Brian Sidebotham (brian-sidebotham)]

A project can contain a schematic (hierarchical or otherwise) and a PCB to
suit the schematic.

If you need multiple PCBs, create a project for each PCB.

Certainly a SMT and TH board is not the same project, they are two
different;The same is true of Tx/Rx projects, each end is a project - they
are different.

Best Regards,

Brian.

[Nimo (nimo-labs)]

Just a thought, is it possible that you are confusing Kicad's idea of a project, with the workspaces found in other packages?

In nearly all packages I have used both for software and hardware development, a project contains 1 schematic (possibly with multiple pages) and one pcb, or for SW packages the code, libraries etc. for creating one executable.
Some packages then take this one step further with the concept of Workspaces (or Solutions in Visual Studio). A workspace can contain multiple projects and is often used in scenarios such as yours where you have different but related projects. E.g. the TX and RX ends of a product.

As far as I'm aware, Kicad doesn't have anything that comes close to the idea of a workspace (other that your own file system directory structure) however I'm sure someone will correct me if I'm wrong.

Kind regards
Nick

[Dick Hollenbeck (dickelbeck)]

On Sep 19, 2013 9:41 AM, "Joonas Reunamo" <email address hidden> wrote:
>
> Hello!
>
> This is a major problem in Kicad in my opinion. Project .pro cannot
> contain several schematic .sch files correctly. New schematic files are
> easy to add with "save current sheet as..." and they appear in project
> tree, but added libraries are saved in .pro and new schematic will need
> a new .pro which also appears in the project tree. Not only ugly, but
> confusing and useless as well.
>
> Why there is r .pro if every schematic needs a separate .pro anyway? Why
> not to add the information directly to .sch file then, at least copy-
> paste would work?
>
> In my opinion project should hold several schematic files and a general
> preferences of a full project. Project isn't always just a one .sch and
> one .brd. Often there is multiple boards needed within one project like
> RX and TX sides.

Improvements are possible. But I think this is likely to be one of those
cases where the improvements will have to come from you.

That tends to be how open source evolves.

That was my polite way of saying what I normally say this way: all patches
and purchase orders will be considered carefully.

>
> --
> You received this bug notification because you are a member of KiCad Bug
> Squad, which is subscribed to KiCad.
> https://bugs.launchpad.net/bugs/1082329
>
> Title:
> the use of the project file is inconsistent
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kicad/+bug/1082329/+subscriptions

[Lorenzo Marcantonio (l-marcantonio)]

On Fri, Sep 20, 2013 at 09:11:19AM -0000, Nicholas Dark wrote:
> Just a thought, is it possible that you are confusing Kicad's idea of a
> project, with the workspaces found in other packages?

Simply put, a kicad project is *exactly* like an old SDT project.

1 project = 1 (multisheet) schematic + 1 PCB

(actually a while ago I advocated that projects should simply disappear,
now that there is a working template system)

--
Lorenzo Marcantonio
Logos Srl

[Miguel Angel Ajo (mangelajo)]

I don't see the "projects" going away even with a good template system,

And yes, workspaces are another abstraction level:

Workspace->Project->PCB/SCH.

I admit, that I had that available in al*um but I never made a big use of
it,
as Dick said, it's an open system, so if it's important for you, and you
follow
the coding guidelines, we must be open to accept something like this.

http://www.kicad-pcb.org/display/DEV/KiCad+Development

Miguel Angel Ajo Pelayo
http://www.nbee.es
[phone]
skype: ajoajoajo

2013/9/20 Lorenzo Marcantonio <email address hidden>

> On Fri, Sep 20, 2013 at 09:11:19AM -0000, Nicholas Dark wrote:
> > Just a thought, is it possible that you are confusing Kicad's idea of a
> > project, with the workspaces found in other packages?
>
> Simply put, a kicad project is *exactly* like an old SDT project.
>
> 1 project = 1 (multisheet) schematic + 1 PCB
>
> (actually a while ago I advocated that projects should simply disappear,
> now that there is a working template system)
>
> --
> Lorenzo Marcantonio
> Logos Srl
>
> --
> You received this bug notification because you are a member of KiCad Bug
> Squad, which is subscribed to KiCad.
> https://bugs.launchpad.net/bugs/1082329
>
> Title:
> the use of the project file is inconsistent
>
> Status in KiCad EDA Software Suite:
> New
>
> Bug description:
> I created the project : usbasp
>
> These would have 2 versions of sch : SMD (usbasp_2_0_0.sch) and PDIP
> version (usbasp_1_0_0.sch)
> All library I put in the project file : usbasp.pro to share to all
> schematic ( I have own lib folder).
>
> It also has several version of pcb which also I put the library
> setting on usbasp.pro to share to all board.
>
> but why both sch and pcbnew ask for another project file
> (usbasp_1_0_0.pro and usbasp_2_0_0.pro)? Is that should use the same
> project file?
>
> The bad things is cvpcb which forced to create usb_1_0_0.pro and don't
> even ask for it by default. I must open the net file manually from
> empty cvpcb to force it to save into new project file.
>
> the footprint filter often failed. Maybe it is because I use custom
> library which is not loaded because it think of different project
> file.
>
> kicad BZR 3811 compiled using mingw32 gcc 4.7.0, wxwidget 2.9.3
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kicad/+bug/1082329/+subscriptions
>