Re: [Kicad-developers] Module editor branch merged
By the way: I remember that you had some issues with the fglrx driver - are the problems fixed or do you use KiCad on a different hardware? Regards, Orson On 07/22/2014 12:43 PM, Maciej Sumiński wrote: Hi Jon, Which version of wxWidgets do you use? Are there any steps that could increase the probability of the issue reproduction? Regards, Orson On 07/22/2014 06:56 AM, Jon Neal wrote: I have been getting some sort of drawing issue sporadically when I open the module editor (from pcbnew). I managed to catch a screenshot of what it is doing here (on the right side): http://i.imgur.com/IU9AYHd.png It seems that it is trying to draw the canvas offset from where it really should be. If I mouse over the tool bar on top it will clear the strip where the drop downs are as long as I hover over that area. This has been happening since the module editor was merged in and that screen shot was taken from bzr-5017. Thanks, Jon On Mon, Jul 21, 2014 at 3:28 AM, jp charras wrote: Le 20/07/2014 21:56, Maciej Sumiński a écrit : On 07/15/2014 04:53 PM, jp charras wrote: Le 14/07/2014 16:51, Maciej Sumiński a écrit : Dear Developers, After a period of testing, the module-editor branch [1] has just been merged to the product branch. Besides the conversion of the module editor to GAL Thanks. There is a redraw/refresh issue on Windows only (using wxWidgets 3.0.1). After switching to GAL (one can use only the F11 key to do that) there is no more GAL screen redraw/refresh, after clicking on a menu or a dialog, for instance after clicking on the layer manager, or the PnS dialog setup. This is also true after clicking on the pcbframe main menu or any popup menu. This is the reason one cannot switch to GAL from the main menu. Note also when switching to gal, the first time you switch to gal using the F11 key, there is no GAL screen redraw/refresh. You have to press the F9 and then the F11 key, in order to have a working GAL screen (until you click on a popup menu). When the GAL screen is no more redrawn, just press F9 an then F11 to reactivate the refresh. Hi Jean-Pierre, It turned out that I did not have exactly the same symptoms, but very similar. I have fixed the problem for my system in revision 5012, could you verify it? Regards, Orson Thanks. The refresh issue is gone now. Good work. I noticed a (minor) focus issue on Windows only, when both the pcb editor and the footprint editor are open and their canvas are visible on screen. When the pcb editor is the active frame, if the mouse cursor is moved out the frame and enters the module editor canvas, the module editor is brought to the foreground and become the active window (without any mouse click) It does not happen on Linux. An other issue in module editor in openGL mode: When a new footprint is loaded, it is put to the last mouse cursor position. It should be loaded at position 0, 0. Otherwise, strange thinks can happen (bad position of new added items, old items not on the initial grid, erroneous coordinates shown in dialogs when editing an item...) and can break the footprint in edit. -- Jean-Pierre CHARRAS ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
Hi Jon, Which version of wxWidgets do you use? Are there any steps that could increase the probability of the issue reproduction? Regards, Orson On 07/22/2014 06:56 AM, Jon Neal wrote: I have been getting some sort of drawing issue sporadically when I open the module editor (from pcbnew). I managed to catch a screenshot of what it is doing here (on the right side): http://i.imgur.com/IU9AYHd.png It seems that it is trying to draw the canvas offset from where it really should be. If I mouse over the tool bar on top it will clear the strip where the drop downs are as long as I hover over that area. This has been happening since the module editor was merged in and that screen shot was taken from bzr-5017. Thanks, Jon On Mon, Jul 21, 2014 at 3:28 AM, jp charras wrote: Le 20/07/2014 21:56, Maciej Sumiński a écrit : On 07/15/2014 04:53 PM, jp charras wrote: Le 14/07/2014 16:51, Maciej Sumiński a écrit : Dear Developers, After a period of testing, the module-editor branch [1] has just been merged to the product branch. Besides the conversion of the module editor to GAL Thanks. There is a redraw/refresh issue on Windows only (using wxWidgets 3.0.1). After switching to GAL (one can use only the F11 key to do that) there is no more GAL screen redraw/refresh, after clicking on a menu or a dialog, for instance after clicking on the layer manager, or the PnS dialog setup. This is also true after clicking on the pcbframe main menu or any popup menu. This is the reason one cannot switch to GAL from the main menu. Note also when switching to gal, the first time you switch to gal using the F11 key, there is no GAL screen redraw/refresh. You have to press the F9 and then the F11 key, in order to have a working GAL screen (until you click on a popup menu). When the GAL screen is no more redrawn, just press F9 an then F11 to reactivate the refresh. Hi Jean-Pierre, It turned out that I did not have exactly the same symptoms, but very similar. I have fixed the problem for my system in revision 5012, could you verify it? Regards, Orson Thanks. The refresh issue is gone now. Good work. I noticed a (minor) focus issue on Windows only, when both the pcb editor and the footprint editor are open and their canvas are visible on screen. When the pcb editor is the active frame, if the mouse cursor is moved out the frame and enters the module editor canvas, the module editor is brought to the foreground and become the active window (without any mouse click) It does not happen on Linux. An other issue in module editor in openGL mode: When a new footprint is loaded, it is put to the last mouse cursor position. It should be loaded at position 0, 0. Otherwise, strange thinks can happen (bad position of new added items, old items not on the initial grid, erroneous coordinates shown in dialogs when editing an item...) and can break the footprint in edit. -- Jean-Pierre CHARRAS ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
I have been getting some sort of drawing issue sporadically when I open the module editor (from pcbnew). I managed to catch a screenshot of what it is doing here (on the right side): http://i.imgur.com/IU9AYHd.png It seems that it is trying to draw the canvas offset from where it really should be. If I mouse over the tool bar on top it will clear the strip where the drop downs are as long as I hover over that area. This has been happening since the module editor was merged in and that screen shot was taken from bzr-5017. Thanks, Jon On Mon, Jul 21, 2014 at 3:28 AM, jp charras wrote: > Le 20/07/2014 21:56, Maciej Sumiński a écrit : > > On 07/15/2014 04:53 PM, jp charras wrote: > >> Le 14/07/2014 16:51, Maciej Sumiński a écrit : > >>> Dear Developers, > >>> > >>> After a period of testing, the module-editor branch [1] has just been > >>> merged to the product branch. Besides the conversion of the module > >>> editor to GAL > >> > >> Thanks. > >> > >> There is a redraw/refresh issue on Windows only (using wxWidgets 3.0.1). > >> > >> After switching to GAL (one can use only the F11 key to do that) there > >> is no more GAL screen redraw/refresh, after clicking on a menu or a > >> dialog, for instance after clicking on the layer manager, or the PnS > >> dialog setup. > >> This is also true after clicking on the pcbframe main menu or any popup > >> menu. > >> This is the reason one cannot switch to GAL from the main menu. > >> > >> Note also when switching to gal, the first time you switch to gal using > >> the F11 key, there is no GAL screen redraw/refresh. > >> You have to press the F9 and then the F11 key, in order to have a > >> working GAL screen (until you click on a popup menu). > >> > >> When the GAL screen is no more redrawn, just press F9 an then F11 to > >> reactivate the refresh. > > > > Hi Jean-Pierre, > > > > It turned out that I did not have exactly the same symptoms, but very > > similar. I have fixed the problem for my system in revision 5012, could > > you verify it? > > > > Regards, > > Orson > > > > Thanks. > The refresh issue is gone now. Good work. > > I noticed a (minor) focus issue on Windows only, when both the pcb > editor and the footprint editor are open and their canvas are visible on > screen. > > When the pcb editor is the active frame, if the mouse cursor is moved > out the frame and enters the module editor canvas, the module editor is > brought to the foreground and become the active window (without any > mouse click) It does not happen on Linux. > > An other issue in module editor in openGL mode: > When a new footprint is loaded, it is put to the last mouse cursor > position. > It should be loaded at position 0, 0. > > Otherwise, strange thinks can happen (bad position of new added items, > old items not on the initial grid, erroneous coordinates shown in > dialogs when editing an item...) and can break the footprint in edit. > > -- > Jean-Pierre CHARRAS > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
Le 20/07/2014 21:56, Maciej Sumiński a écrit : > On 07/15/2014 04:53 PM, jp charras wrote: >> Le 14/07/2014 16:51, Maciej Sumiński a écrit : >>> Dear Developers, >>> >>> After a period of testing, the module-editor branch [1] has just been >>> merged to the product branch. Besides the conversion of the module >>> editor to GAL >> >> Thanks. >> >> There is a redraw/refresh issue on Windows only (using wxWidgets 3.0.1). >> >> After switching to GAL (one can use only the F11 key to do that) there >> is no more GAL screen redraw/refresh, after clicking on a menu or a >> dialog, for instance after clicking on the layer manager, or the PnS >> dialog setup. >> This is also true after clicking on the pcbframe main menu or any popup >> menu. >> This is the reason one cannot switch to GAL from the main menu. >> >> Note also when switching to gal, the first time you switch to gal using >> the F11 key, there is no GAL screen redraw/refresh. >> You have to press the F9 and then the F11 key, in order to have a >> working GAL screen (until you click on a popup menu). >> >> When the GAL screen is no more redrawn, just press F9 an then F11 to >> reactivate the refresh. > > Hi Jean-Pierre, > > It turned out that I did not have exactly the same symptoms, but very > similar. I have fixed the problem for my system in revision 5012, could > you verify it? > > Regards, > Orson > Thanks. The refresh issue is gone now. Good work. I noticed a (minor) focus issue on Windows only, when both the pcb editor and the footprint editor are open and their canvas are visible on screen. When the pcb editor is the active frame, if the mouse cursor is moved out the frame and enters the module editor canvas, the module editor is brought to the foreground and become the active window (without any mouse click) It does not happen on Linux. An other issue in module editor in openGL mode: When a new footprint is loaded, it is put to the last mouse cursor position. It should be loaded at position 0, 0. Otherwise, strange thinks can happen (bad position of new added items, old items not on the initial grid, erroneous coordinates shown in dialogs when editing an item...) and can break the footprint in edit. -- Jean-Pierre CHARRAS ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
On 07/15/2014 04:53 PM, jp charras wrote: Le 14/07/2014 16:51, Maciej Sumiński a écrit : Dear Developers, After a period of testing, the module-editor branch [1] has just been merged to the product branch. Besides the conversion of the module editor to GAL Thanks. There is a redraw/refresh issue on Windows only (using wxWidgets 3.0.1). After switching to GAL (one can use only the F11 key to do that) there is no more GAL screen redraw/refresh, after clicking on a menu or a dialog, for instance after clicking on the layer manager, or the PnS dialog setup. This is also true after clicking on the pcbframe main menu or any popup menu. This is the reason one cannot switch to GAL from the main menu. Note also when switching to gal, the first time you switch to gal using the F11 key, there is no GAL screen redraw/refresh. You have to press the F9 and then the F11 key, in order to have a working GAL screen (until you click on a popup menu). When the GAL screen is no more redrawn, just press F9 an then F11 to reactivate the refresh. Hi Jean-Pierre, It turned out that I did not have exactly the same symptoms, but very similar. I have fixed the problem for my system in revision 5012, could you verify it? Regards, Orson ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
Le 16/07/2014 22:30, Maciej Sumiński a écrit : > W dniu 2014-07-15 16:53, jp charras pisze: >> Le 14/07/2014 16:51, Maciej Sumiński a écrit : >>> Dear Developers, >>> >>> After a period of testing, the module-editor branch [1] has just been >>> merged to the product branch. Besides the conversion of the module >>> editor to GAL >> >> Thanks. >> >> There is a redraw/refresh issue on Windows only (using wxWidgets 3.0.1). >> >> After switching to GAL (one can use only the F11 key to do that) there >> is no more GAL screen redraw/refresh, after clicking on a menu or a >> dialog, for instance after clicking on the layer manager, or the PnS >> dialog setup. >> This is also true after clicking on the pcbframe main menu or any popup >> menu. >> This is the reason one cannot switch to GAL from the main menu. >> >> Note also when switching to gal, the first time you switch to gal using >> the F11 key, there is no GAL screen redraw/refresh. >> You have to press the F9 and then the F11 key, in order to have a >> working GAL screen (until you click on a popup menu). >> >> When the GAL screen is no more redrawn, just press F9 an then F11 to >> reactivate the refresh. > > Jean-Pierre, > > Thank you for the report - I have just built KiCad under Windows to > check it and I confirm the symptoms. It is a serious issue that I was > not aware of and noone has reported that before. I will let you know > once I consider it fixed. > > Regards, > Orson > Thanks. Perhaps this info can help you: If I switch the display mode to cairo (F12) (only once is enough), and after switch to opengl (F11), I do not have anymore this redraw/refresh issue. Perhaps a missing init on Windows, which is made when switching to cairo mode ? -- Jean-Pierre CHARRAS ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
On Thu, Jul 17, 2014 at 03:20:51PM -0700, Cirilo Bernardo wrote: > I suspect we will need a separate cutout layer then. For me modules Cutouts *are* board edges, I've done RAST connectors in the past and they worked. The only thing is that you have to align it correctly. -- Lorenzo Marcantonio Logos Srl ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
On 07/18/2014 05:30 AM, Cirilo Bernardo wrote: - Original Message - From: Dick Hollenbeck To: kicad-developers@lists.launchpad.net Cc: Sent: Friday, July 18, 2014 11:49 AM Subject: Re: [Kicad-developers] Module editor branch merged On 07/17/2014 05:20 PM, Cirilo Bernardo wrote: - Original Message - From: Lorenzo Marcantonio To: Kicad Developers Cc: Sent: Thursday, July 17, 2014 4:27 PM Subject: Re: [Kicad-developers] Module editor branch merged On Wed, Jul 16, 2014 at 03:27:44PM -0700, Cirilo Bernardo wrote: How do these PCB edge modules interact with the PCB board edges? Will they be solids or cutouts? What happens when a module with a drawing on the Edges.Cut layer hangs over the edge of a PCB? Just think about merging the edges in the module with these drawn. The resulting behaviour would be the same. What happens when you draw a new edge hanging over the edge of the pcb? I suspect we will need a separate cutout layer then. For me modules are more useful with cutouts rather than solid outlines. A card edge connector for example can have a cutout to ensure that the board edge has the correct shape. This way there will be no confusion about whether a draw segment is a cutout or a solid. At the moment this is inferred by assuming there is a single solid whose outline has a feature with the lowest X value; other segments are then checked for contiguity with this feature and that forms the solid outline - everything else is a cutout. With that logic, a module with a solid outline that hangs off the left edge of the board becomes the board outline and the genuine board outline becomes a cutout. A module extending over any other edge becomes a cutout of the board outline. Or am I confused about how the edges are treated? - Cirilo The day we first talked about this was more than a year ago. On the very same day, 20 minutes later, I spent 20 minutes and added support for it to the specctra export. The Collector class was very convenient for that. I simply gathered up all the segments/graphics on the Edge.Cuts layer, aggregating them into a Collector, and then output them as a specctra board perimeter. My thinking was that it was incumbent on the board perimeter to have gaps in it, which would be filled in by segments from the module on the edge of the board. This would be like for castle-ations. Or an edge connector with notch(es). I don't think you have to make this too complicated. You do not have an ambiguous board perimeter. Your actual *board level* Edge.Cuts graphics would be open. Then entire polygon would then be closed with the addition of the module which closes the gap. You'd have to butt the ends of the graphics. The Edge.Cuts graphics in the module know what their relationship to the accompanying Cu should be. Thanks Dick, I see the logic now, but for me that's pushing a lot of unnecessary work onto the board designer. Let's say a board outline already exists in a DXF or even an IDF file. The user then has to delete and redraw lines to suit the location of the inserted module(s). Having a cutout layer separate from the outline pushes the job of polygon merging onto the software, but I understand that's not a trivial change to the code. I'm not saying we should make such a change, just that there are good reasons to do it. In my particular case I'll just adapt as needed for the task, using modules with outlines where convenient and avoiding them when doing so will make life easier. The upshot to not changing anything is that the VRML and IDF export code won't be broken so I won't have to touch that code. - Cirilo Hi Cirilo, The reason why we wanted to add Edge.Cuts drawings to modules is to make it easier to use edge connectors. Often they are supposed to be located in a specific distance from an edge. Now you can store the distance in a module file by adding an edge inside. You can still prepare your boards in the way you have suggested - insert a DXF outline and align connectors by hand. There is no reason to move the Edge.Cuts lines to modules if you are not going to reuse them. On the other hand, if you know that you will have to align them more than once, then there is a good reason to draw Edge.Cuts in the module editor. I have seen that similar effect may be achieved by drawing edges on F.SilkS layer (check demos/video/video.kicad_pcb), but then you have to redraw them in the layout editor. I have also read about cases when users draw edges on the silkscreen layer in the module editor and then moved the drawing to Edge.Cuts layer with a text editor. Regards, Orson ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
- Original Message - > From: Dick Hollenbeck > To: kicad-developers@lists.launchpad.net > Cc: > Sent: Friday, July 18, 2014 11:49 AM > Subject: Re: [Kicad-developers] Module editor branch merged > > On 07/17/2014 05:20 PM, Cirilo Bernardo wrote: >> - Original Message - >> >>> From: Lorenzo Marcantonio >>> To: Kicad Developers >>> Cc: >>> Sent: Thursday, July 17, 2014 4:27 PM >>> Subject: Re: [Kicad-developers] Module editor branch merged >>> >>> On Wed, Jul 16, 2014 at 03:27:44PM -0700, Cirilo Bernardo wrote: >>>> How do these PCB edge modules interact with the PCB board edges? >>>> Will they be solids or cutouts? What happens when a module with >>>> a drawing on the Edges.Cut layer hangs over the edge of a PCB? >>> >>> Just think about merging the edges in the module with these drawn. >>> >>> The resulting behaviour would be the same. >>> >>> What happens when you draw a new edge hanging over the edge of the pcb? >>> >> >> >> I suspect we will need a separate cutout layer then. For me modules >> are more useful with cutouts rather than solid outlines. A card edge >> connector for example can have a cutout to ensure that the board edge >> has the correct shape. This way there will be no confusion about whether >> a draw segment is a cutout or a solid. At the moment this is inferred >> by assuming there is a single solid whose outline has a feature with the >> lowest X value; other segments are then checked for contiguity with this >> feature and that forms the solid outline - everything else is a cutout. >> With that logic, a module with a solid outline that hangs off the left >> edge of the board becomes the board outline and the genuine board >> outline becomes a cutout. A module extending over any other edge becomes >> a cutout of the board outline. Or am I confused about how the edges >> are treated? >> >> - Cirilo > > > The day we first talked about this was more than a year ago. On the very > same > day, 20 > minutes later, I spent 20 minutes and added support for it to the specctra > export. The > Collector class was very convenient for that. I simply gathered up all the > segments/graphics on the Edge.Cuts layer, aggregating them into a Collector, > and > then > output them as a specctra board perimeter. > > My thinking was that it was incumbent on the board perimeter to have gaps in > it, > which > would be filled in by segments from the module on the edge of the board. > This > would be > like for castle-ations. Or an edge connector with notch(es). > > I don't think you have to make this too complicated. You do not have an > ambiguous board > perimeter. Your actual *board level* Edge.Cuts graphics would be open. Then > entire > polygon would then be closed with the addition of the module which closes the > gap. You'd > have to butt the ends of the graphics. > > The Edge.Cuts graphics in the module know what their relationship to the > accompanying Cu > should be. > Thanks Dick, I see the logic now, but for me that's pushing a lot of unnecessary work onto the board designer. Let's say a board outline already exists in a DXF or even an IDF file. The user then has to delete and redraw lines to suit the location of the inserted module(s). Having a cutout layer separate from the outline pushes the job of polygon merging onto the software, but I understand that's not a trivial change to the code. I'm not saying we should make such a change, just that there are good reasons to do it. In my particular case I'll just adapt as needed for the task, using modules with outlines where convenient and avoiding them when doing so will make life easier. The upshot to not changing anything is that the VRML and IDF export code won't be broken so I won't have to touch that code. - Cirilo ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
On 07/17/2014 05:20 PM, Cirilo Bernardo wrote: > - Original Message - > >> From: Lorenzo Marcantonio >> To: Kicad Developers >> Cc: >> Sent: Thursday, July 17, 2014 4:27 PM >> Subject: Re: [Kicad-developers] Module editor branch merged >> >> On Wed, Jul 16, 2014 at 03:27:44PM -0700, Cirilo Bernardo wrote: >>> How do these PCB edge modules interact with the PCB board edges? >>> Will they be solids or cutouts? What happens when a module with >>> a drawing on the Edges.Cut layer hangs over the edge of a PCB? >> >> Just think about merging the edges in the module with these drawn. >> >> The resulting behaviour would be the same. >> >> What happens when you draw a new edge hanging over the edge of the pcb? >> > > > I suspect we will need a separate cutout layer then. For me modules > are more useful with cutouts rather than solid outlines. A card edge > connector for example can have a cutout to ensure that the board edge > has the correct shape. This way there will be no confusion about whether > a draw segment is a cutout or a solid. At the moment this is inferred > by assuming there is a single solid whose outline has a feature with the > lowest X value; other segments are then checked for contiguity with this > feature and that forms the solid outline - everything else is a cutout. > With that logic, a module with a solid outline that hangs off the left > edge of the board becomes the board outline and the genuine board > outline becomes a cutout. A module extending over any other edge becomes > a cutout of the board outline. Or am I confused about how the edges > are treated? > > - Cirilo The day we first talked about this was more than a year ago. On the very same day, 20 minutes later, I spent 20 minutes and added support for it to the specctra export. The Collector class was very convenient for that. I simply gathered up all the segments/graphics on the Edge.Cuts layer, aggregating them into a Collector, and then output them as a specctra board perimeter. My thinking was that it was incumbent on the board perimeter to have gaps in it, which would be filled in by segments from the module on the edge of the board. This would be like for castle-ations. Or an edge connector with notch(es). I don't think you have to make this too complicated. You do not have an ambiguous board perimeter. Your actual *board level* Edge.Cuts graphics would be open. Then entire polygon would then be closed with the addition of the module which closes the gap. You'd have to butt the ends of the graphics. The Edge.Cuts graphics in the module know what their relationship to the accompanying Cu should be. ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
- Original Message - > From: Lorenzo Marcantonio > To: Kicad Developers > Cc: > Sent: Thursday, July 17, 2014 4:27 PM > Subject: Re: [Kicad-developers] Module editor branch merged > > On Wed, Jul 16, 2014 at 03:27:44PM -0700, Cirilo Bernardo wrote: >> How do these PCB edge modules interact with the PCB board edges? >> Will they be solids or cutouts? What happens when a module with >> a drawing on the Edges.Cut layer hangs over the edge of a PCB? > > Just think about merging the edges in the module with these drawn. > > The resulting behaviour would be the same. > > What happens when you draw a new edge hanging over the edge of the pcb? > I suspect we will need a separate cutout layer then. For me modules are more useful with cutouts rather than solid outlines. A card edge connector for example can have a cutout to ensure that the board edge has the correct shape. This way there will be no confusion about whether a draw segment is a cutout or a solid. At the moment this is inferred by assuming there is a single solid whose outline has a feature with the lowest X value; other segments are then checked for contiguity with this feature and that forms the solid outline - everything else is a cutout. With that logic, a module with a solid outline that hangs off the left edge of the board becomes the board outline and the genuine board outline becomes a cutout. A module extending over any other edge becomes a cutout of the board outline. Or am I confused about how the edges are treated? - Cirilo ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
On Wed, Jul 16, 2014 at 03:27:44PM -0700, Cirilo Bernardo wrote: > How do these PCB edge modules interact with the PCB board edges? > Will they be solids or cutouts? What happens when a module with > a drawing on the Edges.Cut layer hangs over the edge of a PCB? Just think about merging the edges in the module with these drawn. The resulting behaviour would be the same. What happens when you draw a new edge hanging over the edge of the pcb? -- Lorenzo Marcantonio Logos Srl ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
- Original Message - > From: Maciej Sumiński > To: Kicad Developers > Cc: > Sent: Wednesday, July 16, 2014 6:33 PM > Subject: Re: [Kicad-developers] Module editor branch merged > [snip] > > In GAL editor you can have PCB edges in modules. There was not much code > to be added to handle this, unless I have forgotten about something. If > you are interested in details, have a look at commit 4987.1.84. > How do these PCB edge modules interact with the PCB board edges? Will they be solids or cutouts? What happens when a module with a drawing on the Edges.Cut layer hangs over the edge of a PCB? - Cirilo ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
W dniu 2014-07-15 16:53, jp charras pisze: Le 14/07/2014 16:51, Maciej Sumiński a écrit : Dear Developers, After a period of testing, the module-editor branch [1] has just been merged to the product branch. Besides the conversion of the module editor to GAL Thanks. There is a redraw/refresh issue on Windows only (using wxWidgets 3.0.1). After switching to GAL (one can use only the F11 key to do that) there is no more GAL screen redraw/refresh, after clicking on a menu or a dialog, for instance after clicking on the layer manager, or the PnS dialog setup. This is also true after clicking on the pcbframe main menu or any popup menu. This is the reason one cannot switch to GAL from the main menu. Note also when switching to gal, the first time you switch to gal using the F11 key, there is no GAL screen redraw/refresh. You have to press the F9 and then the F11 key, in order to have a working GAL screen (until you click on a popup menu). When the GAL screen is no more redrawn, just press F9 an then F11 to reactivate the refresh. Jean-Pierre, Thank you for the report - I have just built KiCad under Windows to check it and I confirm the symptoms. It is a serious issue that I was not aware of and noone has reported that before. I will let you know once I consider it fixed. Regards, Orson ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
Hi Orson, very nice work, this gets KiCad to a new level. In my opinion custom pad shapes are for today's PCB designs a important feature. There are some parts like MEMS microphones which require arcs as pads. Do you have any access to professional tools like Altium Designer or Mentor Graphics Expedition for inspirations how that works? (I've used both) Many tools have a separate padstack editor. This video shows how complex pad shapes can be created using the Altium Designer: http://www.newelectronics.co.uk/electronics-videos/altium-design-secret-four-creating-custom-pad-shapes/43959 Also zones can be useful for modules, such as keepout areas. Maybe that's something for a wishlist. Bye, Torsten Gesendet: Mittwoch, 16. Juli 2014 um 10:16 Uhr Von: "Maciej Sumiński" An: kicad-developers@lists.launchpad.net Betreff: Re: [Kicad-developers] Module editor branch merged On 07/16/2014 10:08 AM, Nick Østergaard wrote: > 2014-07-15 17:45 GMT+02:00 Maciej Sumiński : >> Hi Nick, >> >> In my opinion drawing on copper layers with drawing tools instead of laying >> out tracks should not be allowed unless it is supported by the DRC >> algorithm. > > Sure, the DRC should handle it, but refresh my memory -- as far as I > remember there was some talk about including tracks in footprints. I > don't remember the outcome of that or it it is allow or not. For the time being tracks are not supported by the module editor. The reason is the same as - it would have to be handled by all algorithms use tracks as input data (DRC, ratsnest, just to give an example). It could be relatively easy to implement using iterators that go through the list of tracks that belong to a board and then do the same for all tracks that are stored in modules placed on the same board. It is just an idea that may need some further consideration - I do not volunteer to code it now. Regards, Orson >>> 6. no new update yet >> >> Fix pushed to the product branch. > > Yep works now by giving no error. > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
On Wed, Jul 16, 2014 at 11:50:12AM +0200, jp charras wrote: > Therefore you cannot easily take in account (in DRC algorithms) segments > and zones drawn in footprint editor on copper layers, because in many > case they connect 2 different nets. I use this behaviour *exactly* to make equipotential ground point (star-joins) between GND/AGND/EARTH whatever. A couple of pads and a track drawn in between on copper. Completely agree that's a tricky issue; just pointing out the irregularities in the type hierarchy -- Lorenzo Marcantonio Logos Srl ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
On Wed, Jul 16, 2014 at 12:04:53PM +0200, Maciej Sumiński wrote: > I was aware of that, therefore I conducted my tests on boards that contained > modules with Edge.Cuts line inside (not just in the module editor). I > slightly modified one condition in zone filling algorithm to take edges in > modules into account. > Other tests went without any problems: printing Edge.Cuts layer, plotting > (PDF & Gerbers), SVG export, Specctra export & 3D viewer. Does anything else > comes to your mind? IIRC Dick also said that should have been a simple modification, however he didn't have time for it. Nothing else using edges comes to my mind... -- Lorenzo Marcantonio Logos Srl ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
On Wed, Jul 16, 2014 at 11:29:58AM +0200, Tomasz Wlostowski wrote: > Do you mean storing everything in a flat hierarchy and getting rid of all > links/pointers between items? This would be great (Alfons uses such model in > Freerouter, I made it to less extent in our P&S). Not necessarily flat, the containment hierarchy between board/module/item is useful and it's practical to traverse it recursively (a depth first usually would be appropriate and you don't need to support nested modules --- altough in theory at the moment you should:P). Also our trees are threaded so it's easy to iterate non recursively on them...remember than most operation on the board are simply linear list scans at the moment. What I mean is that while a MODULE contains BOARD_ITEMs (in m_Drawings), in general BOARD_ITEMs can't be put in a MODULE (and that's horrible from type theory itself :P). Well, in fact BOARD is-a BOARD_ITEM and that would made Cantor roll in its coffin... In fact at least a DRAWSEGMENT works both in the board and in a module. I remembered different types. Other than that, why we need a difference between TEXTE_MODULE and TEXTE_PCB? why TRACK is not a DRAWSEGMENT (or if the is-a doesn't hold, why can't we have a TRACK in a module? I know, the track list need to be kept sorted by netlist, it was a rethoric question) some refactoring in the class hierarchy/usage could help with these problems and allow other proposed extensions (like zones in modules). So in the end the irregular type system gives issues (not very harmful ones, at least) -- Lorenzo Marcantonio Logos Srl ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
On 07/16/2014 11:01 AM, Lorenzo Marcantonio wrote: On Wed, Jul 16, 2014 at 10:33:06AM +0200, Maciej Sumiński wrote: Are not they added as DRAWSEGMENTs on copper layers? I am willing to bet that it is not handled by DRC. I'm not accepting that bet :D Why the track are not subclasses of segments is probably an old design decision. Also because in that case arc tracks would need do be handled (not that it would be a bad idea...) In GAL editor you can have PCB edges in modules. There was not much code to be added to handle this, unless I have forgotten about something. If you are interested in details, have a look at commit 4987.1.84. The old code also allowed this; is the rest of pcbnew that doesn't collate pcb edges from modules with the ones in the board; an explicit mechanism was added to the layer selector to *avoid* it being selectable in the module editor. I was aware of that, therefore I conducted my tests on boards that contained modules with Edge.Cuts line inside (not just in the module editor). I slightly modified one condition in zone filling algorithm to take edges in modules into account. Other tests went without any problems: printing Edge.Cuts layer, plotting (PDF & Gerbers), SVG export, Specctra export & 3D viewer. Does anything else comes to your mind? Regards, Orson Just another reason to have some kind of unified type for stuff in the board and in the modules (IIRC another CERN proposal of not a lot of time ago). ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
Le 16/07/2014 10:16, Maciej Sumiński a écrit : > On 07/16/2014 10:08 AM, Nick Østergaard wrote: >> 2014-07-15 17:45 GMT+02:00 Maciej Sumiński : >>> Hi Nick, >>> >>> In my opinion drawing on copper layers with drawing tools instead of >>> laying >>> out tracks should not be allowed unless it is supported by the DRC >>> algorithm. >> >> Sure, the DRC should handle it, but refresh my memory -- as far as I >> remember there was some talk about including tracks in footprints. I >> don't remember the outcome of that or it it is allow or not. > > For the time being tracks are not supported by the module editor. The > reason is the same as - it would have to be handled by all algorithms > use tracks as input data (DRC, ratsnest, just to give an example). > It could be relatively easy to implement using iterators that go through > the list of tracks that belong to a board and then do the same for all > tracks that are stored in modules placed on the same board. It is just > an idea that may need some further consideration - I do not volunteer to > code it now. > > Regards, > Orson > Some thought about tracks/segments/zones on copper layers in Footprint editor. If tracks are allowed in footprints, handling them in DRC and ratsnest is perhaps the most easy part of the needed code (except for microwave applications). But there are many tricky issues: * When you create a footprint, you don't know anything about layers count, anything about design constraints ( net classes constraints, track width, clearance, impedance which need to know the thickness of the substrate between 2 layers ...) and nets. How can you design a good footprint with tracks with no knowledge of these constraints? * When the footprint is put on the board, what do you do when this footprint is moved, flipped ... What about tracks created by the footprint editor, what about new tracks connected to these predefined tracks? * What do you do when modifying predefined tracks, and when you update this footprint (exchange function) from the footprint library? 1 - You have to take *good* decisions about these tricky issues. this is not easy. 2 - I also do not volunteer to code it, never. 3 - Moreover, I am thinking using tracks in footprints creates many issues and have only very few advantages. Note also using tracks (or segments, like now) in microwave footprints is very very tricky for DRC tests. The basic reason is the fact tracks and zones in DRC tests are expected to be equipotential copper areas. *This is not the fact* in microwave footprints. Therefore you cannot easily take in account (in DRC algorithms) segments and zones drawn in footprint editor on copper layers, because in many case they connect 2 different nets. In fact these shapes drawn on the copper layers are something like inductors, capacitors, and sometimes more complex passive structures, like filters. -- Jean-Pierre CHARRAS ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
On 16.07.2014 11:01, Lorenzo Marcantonio wrote: On Wed, Jul 16, 2014 at 10:33:06AM +0200, Maciej Sumiński wrote: Are not they added as DRAWSEGMENTs on copper layers? I am willing to bet that it is not handled by DRC. I'm not accepting that bet :D Why the track are not subclasses of segments is probably an old design decision. Also because in that case arc tracks would need do be handled (not that it would be a bad idea...) In GAL editor you can have PCB edges in modules. There was not much code to be added to handle this, unless I have forgotten about something. If you are interested in details, have a look at commit 4987.1.84. The old code also allowed this; is the rest of pcbnew that doesn't collate pcb edges from modules with the ones in the board; an explicit mechanism was added to the layer selector to *avoid* it being selectable in the module editor. Just another reason to have some kind of unified type for stuff in the board and in the modules (IIRC another CERN proposal of not a lot of time ago). Do you mean storing everything in a flat hierarchy and getting rid of all links/pointers between items? This would be great (Alfons uses such model in Freerouter, I made it to less extent in our P&S). Cheers, Tom ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
On Wed, Jul 16, 2014 at 10:33:06AM +0200, Maciej Sumiński wrote: > Are not they added as DRAWSEGMENTs on copper layers? I am willing to bet > that it is not handled by DRC. I'm not accepting that bet :D Why the track are not subclasses of segments is probably an old design decision. Also because in that case arc tracks would need do be handled (not that it would be a bad idea...) > In GAL editor you can have PCB edges in modules. There was not much code to > be added to handle this, unless I have forgotten about something. If you are > interested in details, have a look at commit 4987.1.84. The old code also allowed this; is the rest of pcbnew that doesn't collate pcb edges from modules with the ones in the board; an explicit mechanism was added to the layer selector to *avoid* it being selectable in the module editor. Just another reason to have some kind of unified type for stuff in the board and in the modules (IIRC another CERN proposal of not a lot of time ago). -- Lorenzo Marcantonio Logos Srl ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
On 07/16/2014 10:11 AM, Lorenzo Marcantonio wrote: On Wed, Jul 16, 2014 at 10:08:17AM +0200, Nick Østergaard wrote: Sure, the DRC should handle it, but refresh my memory -- as far as I remember there was some talk about including tracks in footprints. I don't remember the outcome of that or it it is allow or not. AFAIK tracks in footprints are already allowed (it gives a fat warning however), since they are used by the microwave tools. No idea if they are properly collated for DRC. Are not they added as DRAWSEGMENTs on copper layers? I am willing to bet that it is not handled by DRC. Could be a problem similar to the famous 'no PCB edges in modules' In GAL editor you can have PCB edges in modules. There was not much code to be added to handle this, unless I have forgotten about something. If you are interested in details, have a look at commit 4987.1.84. Regards, Orson ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
On Wed, Jul 16, 2014 at 10:08:17AM +0200, Nick Østergaard wrote: > Sure, the DRC should handle it, but refresh my memory -- as far as I > remember there was some talk about including tracks in footprints. I > don't remember the outcome of that or it it is allow or not. AFAIK tracks in footprints are already allowed (it gives a fat warning however), since they are used by the microwave tools. No idea if they are properly collated for DRC. Could be a problem similar to the famous 'no PCB edges in modules' -- Lorenzo Marcantonio Logos Srl ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
On 07/16/2014 10:08 AM, Nick Østergaard wrote: 2014-07-15 17:45 GMT+02:00 Maciej Sumiński : Hi Nick, In my opinion drawing on copper layers with drawing tools instead of laying out tracks should not be allowed unless it is supported by the DRC algorithm. Sure, the DRC should handle it, but refresh my memory -- as far as I remember there was some talk about including tracks in footprints. I don't remember the outcome of that or it it is allow or not. For the time being tracks are not supported by the module editor. The reason is the same as - it would have to be handled by all algorithms use tracks as input data (DRC, ratsnest, just to give an example). It could be relatively easy to implement using iterators that go through the list of tracks that belong to a board and then do the same for all tracks that are stored in modules placed on the same board. It is just an idea that may need some further consideration - I do not volunteer to code it now. Regards, Orson 6. no new update yet Fix pushed to the product branch. Yep works now by giving no error. ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
2014-07-15 17:45 GMT+02:00 Maciej Sumiński : > Hi Nick, > > In my opinion drawing on copper layers with drawing tools instead of laying > out tracks should not be allowed unless it is supported by the DRC > algorithm. Sure, the DRC should handle it, but refresh my memory -- as far as I remember there was some talk about including tracks in footprints. I don't remember the outcome of that or it it is allow or not. >> 6. no new update yet > > Fix pushed to the product branch. Yep works now by giving no error. ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
On 07/15/2014 04:57 PM, Nick Østergaard wrote: Hi all Just FYI, orson has been working hard today, and he has looking into those and other bugs, and fixed them. Thank you Maciej. 1. fixed in 4997 2. fixed in 5001 3. not really a bug, just non intuitive for me 4. not a bug 5. no new update yet Hi Nick, In my opinion drawing on copper layers with drawing tools instead of laying out tracks should not be allowed unless it is supported by the DRC algorithm. 6. no new update yet Fix pushed to the product branch. 7. meh 8. could not reproduce Neither could I, but if someone finds a way to recreate the bug - please let me know. Regards, Orson 2014-07-14 22:54 GMT+02:00 Nick Østergaard : Hi Orson I will just comment with the bugs/observations I found, that we discussed on IRC. This is just for reference, if someone notices in the meantime, and for easier reference for you. Other than that, as I told you it seems quite stable otherwise, no crashes or anything :) 1. P&S dialog too small per default, and can be resized smaller than the controlls on it. 2. When trying to move a pad or a graphic element in the module editor it gives the pad a wierd offset, maybe because the footprint anchor has been moved by me. Need more testing. 3. Enumeration cannot add the prefix. 4. Deleting in GAL needs still to be implemented. 5. I am not allowed to initialte a drawing on a copper layer, but I can change it from a silk layer in the graphic items properties, this is inconsistent. 6. If editing a module from a pcb, then if the module is locked in the pcb, the graphic elements are also locked in the module editor. It says "Selection contains locked items. Do you want to continue?" 7. There is no tooltip for the selection tool, not in default or GAL, but I think there should be one, maybe just "Selection tool". 8. I did notice one occourence where I could not deselect the pads. Not sure why or how. Needs more testing. Nick Østergaard 2014-07-14 17:07 GMT+02:00 Dick Hollenbeck : On 07/14/2014 09:51 AM, Maciej Sumiński wrote: Dear Developers, After a period of testing, the module-editor branch [1] has just been merged to the product branch. Besides the conversion of the module editor to GAL, we have also: - added a basic context menu to handle zones - added support for the "locked" property of modules - fixed layer switching after a via placement in the PNS router - enabled display for module anchors - removed panning area limit Some of the changes were possible thanks to reports from you, therefore I am grateful to the reporters. Kind regards, Orson 1. http://www.ohwr.org/projects/cern-kicad/wiki/ModuleEditor Wow. Great stuff. Thanks Tom and Orson. ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
Hi all Just FYI, orson has been working hard today, and he has looking into those and other bugs, and fixed them. Thank you Maciej. 1. fixed in 4997 2. fixed in 5001 3. not really a bug, just non intuitive for me 4. not a bug 5. no new update yet 6. no new update yet 7. meh 8. could not reproduce 2014-07-14 22:54 GMT+02:00 Nick Østergaard : > Hi Orson > > I will just comment with the bugs/observations I found, that we > discussed on IRC. This is just for reference, if someone notices in > the meantime, and for easier reference for you. Other than that, as I > told you it seems quite stable otherwise, no crashes or anything :) > > 1. P&S dialog too small per default, and can be resized smaller than > the controlls on it. > 2. When trying to move a pad or a graphic element in the module editor > it gives the pad a wierd offset, maybe because the footprint anchor > has been moved by me. Need more testing. > 3. Enumeration cannot add the prefix. > 4. Deleting in GAL needs still to be implemented. > 5. I am not allowed to initialte a drawing on a copper layer, but I > can change it from a silk layer in the graphic items properties, this > is inconsistent. > 6. If editing a module from a pcb, then if the module is locked in the > pcb, the graphic elements are also locked in the module editor. It > says "Selection contains locked items. Do you want to continue?" > 7. There is no tooltip for the selection tool, not in default or GAL, > but I think there should be one, maybe just "Selection tool". > 8. I did notice one occourence where I could not deselect the pads. > Not sure why or how. Needs more testing. > > Nick Østergaard > > 2014-07-14 17:07 GMT+02:00 Dick Hollenbeck : >> On 07/14/2014 09:51 AM, Maciej Sumiński wrote: >>> Dear Developers, >>> >>> After a period of testing, the module-editor branch [1] has just been >>> merged to the product branch. Besides the conversion of the module >>> editor to GAL, we have also: >>> - added a basic context menu to handle zones >>> - added support for the "locked" property of modules >>> - fixed layer switching after a via placement in the PNS router >>> - enabled display for module anchors >>> - removed panning area limit >>> >>> Some of the changes were possible thanks to reports from you, therefore >>> I am grateful to the reporters. >>> >>> Kind regards, >>> Orson >>> >>> 1. http://www.ohwr.org/projects/cern-kicad/wiki/ModuleEditor >> >> Wow. Great stuff. Thanks Tom and Orson. >> >> >> >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
Le 14/07/2014 16:51, Maciej Sumiński a écrit : > Dear Developers, > > After a period of testing, the module-editor branch [1] has just been > merged to the product branch. Besides the conversion of the module > editor to GAL Thanks. There is a redraw/refresh issue on Windows only (using wxWidgets 3.0.1). After switching to GAL (one can use only the F11 key to do that) there is no more GAL screen redraw/refresh, after clicking on a menu or a dialog, for instance after clicking on the layer manager, or the PnS dialog setup. This is also true after clicking on the pcbframe main menu or any popup menu. This is the reason one cannot switch to GAL from the main menu. Note also when switching to gal, the first time you switch to gal using the F11 key, there is no GAL screen redraw/refresh. You have to press the F9 and then the F11 key, in order to have a working GAL screen (until you click on a popup menu). When the GAL screen is no more redrawn, just press F9 an then F11 to reactivate the refresh. -- Jean-Pierre CHARRAS ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
Hi Orson I will just comment with the bugs/observations I found, that we discussed on IRC. This is just for reference, if someone notices in the meantime, and for easier reference for you. Other than that, as I told you it seems quite stable otherwise, no crashes or anything :) 1. P&S dialog too small per default, and can be resized smaller than the controlls on it. 2. When trying to move a pad or a graphic element in the module editor it gives the pad a wierd offset, maybe because the footprint anchor has been moved by me. Need more testing. 3. Enumeration cannot add the prefix. 4. Deleting in GAL needs still to be implemented. 5. I am not allowed to initialte a drawing on a copper layer, but I can change it from a silk layer in the graphic items properties, this is inconsistent. 6. If editing a module from a pcb, then if the module is locked in the pcb, the graphic elements are also locked in the module editor. It says "Selection contains locked items. Do you want to continue?" 7. There is no tooltip for the selection tool, not in default or GAL, but I think there should be one, maybe just "Selection tool". 8. I did notice one occourence where I could not deselect the pads. Not sure why or how. Needs more testing. Nick Østergaard 2014-07-14 17:07 GMT+02:00 Dick Hollenbeck : > On 07/14/2014 09:51 AM, Maciej Sumiński wrote: >> Dear Developers, >> >> After a period of testing, the module-editor branch [1] has just been >> merged to the product branch. Besides the conversion of the module >> editor to GAL, we have also: >> - added a basic context menu to handle zones >> - added support for the "locked" property of modules >> - fixed layer switching after a via placement in the PNS router >> - enabled display for module anchors >> - removed panning area limit >> >> Some of the changes were possible thanks to reports from you, therefore >> I am grateful to the reporters. >> >> Kind regards, >> Orson >> >> 1. http://www.ohwr.org/projects/cern-kicad/wiki/ModuleEditor > > Wow. Great stuff. Thanks Tom and Orson. > > > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Module editor branch merged
On 07/14/2014 09:51 AM, Maciej Sumiński wrote: > Dear Developers, > > After a period of testing, the module-editor branch [1] has just been > merged to the product branch. Besides the conversion of the module > editor to GAL, we have also: > - added a basic context menu to handle zones > - added support for the "locked" property of modules > - fixed layer switching after a via placement in the PNS router > - enabled display for module anchors > - removed panning area limit > > Some of the changes were possible thanks to reports from you, therefore > I am grateful to the reporters. > > Kind regards, > Orson > > 1. http://www.ohwr.org/projects/cern-kicad/wiki/ModuleEditor Wow. Great stuff. Thanks Tom and Orson. ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
