pcb-bugs — Bug reports and patch submission notification list

[Pcb-bugs] [Bug 1982762] Re: centroid file orientations wrong on some elements

[Bert T. <19...@bu...>]

Hi Jiří,

I added the text you proposed.

Kind regards,

Bert Timmerman.

** Changed in: pcb
       Status: In Progress => Fix Committed

** Changed in: pcb
   Importance: Undecided => Low

** Changed in: pcb
    Milestone: None => pcb-4.3.1

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/1982762

Title:
  centroid file orientations wrong on some elements

Status in pcb:
  Fix Committed

Bug description:
  The centroid (XY) file generation gives wrong orientation on some
  elements (i.e. different from other similar elements on the board).
  I'm using PCB version 4.2.2 and just started to send centroid files to
  a supplier, so I didn't check this in previous versions.

  Sometimes I need to use more overlapping pads (with the same pin
  number), namely to build more complex pad shapes, and/or to compensate
  for unwanted offsets in the element centre coordinates (when the
  element have more pins on one side than the other, such as some
  connectors, SOT-23, SOT-223, TO-220 etc., the calculation based on
  average of all pads coordinates just doesn't work properly, so I must
  use multiple overlaying pads on the less populated side of the case to
  balance the calculated center to the correct point of the element).
  This is not really convenient, but it works.

  The real problem is, that SOME elements (possibly the mentioned ones
  with multiple pads "1", but I'm not 100% sure about the mechanism
  here) have the orientation in centroid file different from other
  similar components, usually offset by +90°.

  Please see the attached example. There are 3 diodes with the same
  orientation. D1 is designed to allow for both SMD and through-hole
  versions of the component, hence it contains both pins and pads, plus
  another pair of pads interconnecting these. In contrast, D3 is a
  simple SMD component with just a pair of pads. Since both have
  pins/pads #1 down, are perfectly symmetric and all pins/pads are on
  the y-axis of the element, I would expect the generated orientation to
  be the same.

  In reality, D1 gives 180° and D3 gives 90°, so a manual edit to the
  centroid file is needed for proper board assembly.

  Also note, that deletion of extra pins/pads corrects the problem: D2
  is a copy of D1, only just 2 pins and 2 pads got deleted (in .pcb file
  using a text editor), now the orientation is correct (90°). I also
  tried to reorder the pin/pad definitions in the .pcb file, and to
  delete just one pair of extra pins/pads, but no luck there...

  Thanks a lot for any attention to this issue.

  (Note that silkscreen lines overlapping pads are of no concern here,
  as the silkscreen layer is printed just as a paper document, not on
  the board.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/1982762/+subscriptions

[Pcb-bugs] [Bug 2019912] Re: Make GAF scheme dir compatible with Lepton EDA

[Bert T. <20...@bu...>]

Hi Ahmed,

I just tested your patch and found that if I configure with:  --with-
gaf-datadir=${prefix}/gEDA

I get:

xdg data directory:       ${datarootdir}
KDE data directory:       ${datarootdir}
gaf data directory:       /gEDA
dmalloc debugging:        no

I get:

xdg data directory:       ${datarootdir}
KDE data directory:       ${datarootdir}
gaf data directory:       /usr/share/gEDA
dmalloc debugging:        no


when I configure with the absolute path:  --with-gaf-datadir=/usr/share/gEDA

The ${prefix} is omitted in both situations.


Invoking configure without --with-gaf-datadir gives:

xdg data directory:       ${datarootdir}
KDE data directory:       ${datarootdir}
gaf data directory:       ${prefix}/share
dmalloc debugging:        no

Is this intentional ?

Or is this due to another bug ?

Kind regards,

Bert Timmerman

** Changed in: pcb
       Status: New => Triaged

** Changed in: pcb
   Importance: Undecided => Critical

** Changed in: pcb
   Importance: Critical => Low

** Changed in: pcb
     Assignee: (unassigned) => Bert Timmerman (bert-timmerman)

** Changed in: pcb
    Milestone: None => pcb-4.3.1

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/2019912

Title:
  Make GAF scheme dir compatible with Lepton EDA

Status in pcb:
  Triaged

Bug description:
  Hello,

    Debian has replaced gEDA/gaf with Lepton EDA, which is a fork of
  gEDA. So when I built pcb using --with-gaf-datadir=/usr/share/lepton-
  eda, it installed the scheme addition to /usr/share/lepton-
  eda/gEDA/scheme dir ! Which is contrary to what I expected it to do
  (ie. install to /usr/share/lepton-eda/scheme). So I prepared a patch
  to fix this, the patch expects GAFDATADIR to include the gEDA (or
  whatever equivalent tool name). I hope you would accept the patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/2019912/+subscriptions

[Pcb-bugs] [Blueprint rfc] Request For Comments

[api.ng <hd...@gm...>]

Blueprint changed by api.ng:

Whiteboard set to:
_input

-- 
Request For Comments
https://blueprints.launchpad.net/pcb/+spec/rfc

[Pcb-bugs] [Bug 1952989] Re: GTK3 User Interface

[Cesar S. <19...@bu...>]

Hi Bert, just letting you know I recently got back working on the GTK 3
port.

I restarted this from a new direction. Instead of compiling directly to
GTK 3, I'm upgrading the GTK 2 HID to the latest GTK 2 version, while
removing deprecated APIs, and migrating to cairo for rendering. The
advantage is, I can still compile with GTK 2 libraries and see that the
results are correct. There is some overlap between the latest GTK 2 and
GTK 3, which allow me to keep working incrementally on GTK 2 as far as
possible, leaving less work for the actual switch to GTK 3.

So far I'm having promising results.

I have doubts about really updating the actual GTK 2 HID with this work,
since right now it is quite stable, and would make it depend on a newer
GTK 2 version.

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/1952989

Title:
  GTK3 User Interface

Status in pcb:
  Triaged

Bug description:
  pcb requires a GTK3 User Interface sooner or later.

  This bug report (feature request) is raised to serve as the start of a
  topic branch for development.

  Related development issues and decisions for the GTK3 UI shall be
  discussed in this bug report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/1952989/+subscriptions

[Pcb-bugs] [Bug 2073017] Re: site "pcb.geda-project.org" is not accessible

[DJ D. <20...@bu...>]

I rebooted it, again.  It goes down often these days, as the hardware
and software are 14 years old.

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/2073017

Title:
  site "pcb.geda-project.org" is not accessible

Status in pcb:
  Won't Fix

Bug description:
  While [regression building pcb](https://github.com/Homebrew/homebrew-
  core/pull/177196), I found the site (http://pcb.geda-project.org/) is
  not accessible. Raise this issue for awareness. Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/2073017/+subscriptions

[Pcb-bugs] [Bug 2073017] Re: site "pcb.geda-project.org" is not accessible

[Bert T. <20...@bu...>]

** Changed in: pcb
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/2073017

Title:
  site "pcb.geda-project.org" is not accessible

Status in pcb:
  Won't Fix

Bug description:
  While [regression building pcb](https://github.com/Homebrew/homebrew-
  core/pull/177196), I found the site (http://pcb.geda-project.org/) is
  not accessible. Raise this issue for awareness. Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/2073017/+subscriptions

[Pcb-bugs] [Bug 1981481] Re: user interface scaling on HiDPI possible?

[Bert T. <19...@bu...>]

If this issue persists, please inform us and provide screenshots and
relevant information.

** Changed in: pcb
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/1981481

Title:
  user interface scaling on HiDPI possible?

Status in pcb:
  Incomplete

Bug description:
  On July 9th, 2022 Britton Kerin reported on the geda-user mailing
  list:

  I just built 4.3 and the interface is almost unreadably tiny on my
  HiDPI screen.  I tried my normal desperation measure of this script:

  https://github.com/kaueraal/run_scaled

  which gets the tool icons visible but somehow the fonts managed to
  keep themselves the same size only more blurry.

  Anyone come up with a good approach to this?  I get the impression
  that it's hard to get gtk2 software to handle it.

  Britton

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/1981481/+subscriptions

[Pcb-bugs] [Bug 1982762] Re: centroid file orientations wrong on some elements

[Bert T. <19...@bu...>]

** Changed in: pcb
       Status: New => In Progress

** Changed in: pcb
     Assignee: (unassigned) => Bert Timmerman (bert-timmerman)

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/1982762

Title:
  centroid file orientations wrong on some elements

Status in pcb:
  In Progress

Bug description:
  The centroid (XY) file generation gives wrong orientation on some
  elements (i.e. different from other similar elements on the board).
  I'm using PCB version 4.2.2 and just started to send centroid files to
  a supplier, so I didn't check this in previous versions.

  Sometimes I need to use more overlapping pads (with the same pin
  number), namely to build more complex pad shapes, and/or to compensate
  for unwanted offsets in the element centre coordinates (when the
  element have more pins on one side than the other, such as some
  connectors, SOT-23, SOT-223, TO-220 etc., the calculation based on
  average of all pads coordinates just doesn't work properly, so I must
  use multiple overlaying pads on the less populated side of the case to
  balance the calculated center to the correct point of the element).
  This is not really convenient, but it works.

  The real problem is, that SOME elements (possibly the mentioned ones
  with multiple pads "1", but I'm not 100% sure about the mechanism
  here) have the orientation in centroid file different from other
  similar components, usually offset by +90°.

  Please see the attached example. There are 3 diodes with the same
  orientation. D1 is designed to allow for both SMD and through-hole
  versions of the component, hence it contains both pins and pads, plus
  another pair of pads interconnecting these. In contrast, D3 is a
  simple SMD component with just a pair of pads. Since both have
  pins/pads #1 down, are perfectly symmetric and all pins/pads are on
  the y-axis of the element, I would expect the generated orientation to
  be the same.

  In reality, D1 gives 180° and D3 gives 90°, so a manual edit to the
  centroid file is needed for proper board assembly.

  Also note, that deletion of extra pins/pads corrects the problem: D2
  is a copy of D1, only just 2 pins and 2 pads got deleted (in .pcb file
  using a text editor), now the orientation is correct (90°). I also
  tried to reorder the pin/pad definitions in the .pcb file, and to
  delete just one pair of extra pins/pads, but no luck there...

  Thanks a lot for any attention to this issue.

  (Note that silkscreen lines overlapping pads are of no concern here,
  as the silkscreen layer is printed just as a paper document, not on
  the board.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/1982762/+subscriptions

[Pcb-bugs] [Bug 2071650] Re: Import Schematics not working after .scm mod

[Bert T. <20...@bu...>]

Most recent git repository at:  https://github.com/gEDA-pcb-
developers/pcb

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/2071650

Title:
  Import Schematics not working after .scm mod

Status in pcb:
  New

Bug description:
  Not sure if this is a bug or a missing feature.

  Current PCB version, v4.3.0-g9dea9f5a, compiled and installed from
  https://github.com/bgamari/geda-pcb

  I also have a previous version 20140316 on different machine.

  My question; how do I re-load a modified .scm to pcb? In the previous
  version simply selecting "Import Schematic"  loads the changes. The
  same operation in the latest version does nothing.

  How are schematic changes re-loaded?

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/2071650/+subscriptions

[Pcb-bugs] [Bug 2073017] Re: site "pcb.geda-project.org" is not accessible

[Bert T. <20...@bu...>]

AFAICT, the site is (permanently) down.

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/2073017

Title:
  site "pcb.geda-project.org" is not accessible

Status in pcb:
  New

Bug description:
  While [regression building pcb](https://github.com/Homebrew/homebrew-
  core/pull/177196), I found the site (http://pcb.geda-project.org/) is
  not accessible. Raise this issue for awareness. Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/2073017/+subscriptions

[Pcb-bugs] [Bug 699454] Re: Gerber exporter options

[sunflower <69...@bu...>]

fantastic update https://teamnamesed.com/basketball-team-names/

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/699454

Title:
  Gerber exporter options

Status in gEDA project:
  New
Status in pcb:
  New

Bug description:
  Yesterday I talked to a man who made PCBs
  at one of my workplaces. He told me all
  their devices were metric. Also he required
  outline in every layer. So I took the patch
  from feature request 1663208, cleaned it up
  and added some more flexibility.

  In result, additional gerber exporter options are:

  (1) metric output (separately in Gerbers and Excellons)
  (2) 3.3 or 4.2 precision in metric Excellon output,
      0..6 (separately for X and Y axes) in Gerber
  (3) decimal point in Excellon output
  (4) outline in every Gerber (if `outline' layer is present)
  (5) disable drills output in outline layers

To manage notifications about this bug go to:
https://bugs.launchpad.net/geda-project/+bug/699454/+subscriptions

[Pcb-bugs] [Bug 699312] Re: The autorouter is incompatible with the trace optimiser

[sunflower <69...@bu...>]

This is an impressively detailed and well-structured bug report!
https://fmwatasa.com

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/699312

Title:
  The autorouter is incompatible with the trace optimiser

Status in gEDA project:
  Confirmed
Status in pcb:
  Confirmed

Bug description:
  The autorouter creates traces that are incompatible with the trace
  optimiser mitering function.  The attached PCB file shows the problem.

  Affected versions: 
  20091103 compiled from source on Linux
  GIT head downloaded 4th Feb 2010 & compiled on Linux

  Steps to reproduce:
  1. Load attached file
  2. Trace Optimiser -> miter
  3. Observe failure to miter

  Alternate steps to reproduce:
  1. Load attached file
  2. Delete existing traces
  3. Optimise rats 
  4. Select rat
  5. Autoroute selected rat
  6. Trace Optimiser -> miter
  7. Observe failure to miter

  Initial diagnosis
  The autorouter creates traces that have tiny gaps (around 0.01 mils) that prevent mitering.  Loading the attached PCB file shoes that the autorouter creates
  vertical and horizontal lines *mostly* lie on a 1.00 mil grid, but occasionally the lines are off grid by 0.01 or 0.02 mil.  These gaps are generally too small to see,
  but are big enough to prevent the trace optimiser from mitering.

To manage notifications about this bug go to:
https://bugs.launchpad.net/geda-project/+bug/699312/+subscriptions

[Pcb-bugs] [Bug 699203] Re: Undo with the line tool sometimes switches to wrong node

[sunflower <69...@bu...>]

hat's a well-documented and precise bug report

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/699203

Title:
  Undo with the line tool sometimes switches to wrong node

Status in gEDA project:
  New
Status in pcb:
  New

Bug description:
  Undo with the line tool will under certain circumstances
  choose the wrong node to start the next line segment.
  How to reproduce:
   1) set grid to 100 mil
   2) select the line tool
   3) draw a three node triangle: 
       (100/100) to (100/200) to (200/200) to (100/100)
   4) press [u] to undo the last segment
   5) the next segment will start at (100/100) rather than (100/200)

  ---<(kaimartin)>---

To manage notifications about this bug go to:
https://bugs.launchpad.net/geda-project/+bug/699203/+subscriptions

[Pcb-bugs] [Bug 699315] Re: Can not move/copy simple element.

[sunflower <69...@bu...>]

This is a clear and concise report of the issue https://gbwhata.net

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/699315

Title:
  Can not move/copy simple element.

Status in gEDA project:
  Confirmed
Status in pcb:
  Confirmed

Bug description:
  Attached is a very simple board containing a 1mm fiducial.
  (implemented as a single-pad SMT component)

  The component may be selected, but copy and pasting does not work.  It
  is not locked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/geda-project/+bug/699315/+subscriptions

[Pcb-bugs] [Bug 2073017] [NEW] site "pcb.geda-project.org" is not accessible

[Rui C. <20...@bu...>]

Public bug reported:

While [regression building pcb](https://github.com/Homebrew/homebrew-
core/pull/177196), I found the site (http://pcb.geda-project.org/) is
not accessible. Raise this issue for awareness. Thanks!

** Affects: pcb
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/2073017

Title:
  site "pcb.geda-project.org" is not accessible

Status in pcb:
  New

Bug description:
  While [regression building pcb](https://github.com/Homebrew/homebrew-
  core/pull/177196), I found the site (http://pcb.geda-project.org/) is
  not accessible. Raise this issue for awareness. Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/2073017/+subscriptions

[Pcb-bugs] [Bug 2071650] Re: Import Schematics not working after .scm mod

[Charles B. <20...@bu...>]

Not a bug at all. Have to use gsch2pcb instead.

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/2071650

Title:
  Import Schematics not working after .scm mod

Status in pcb:
  New

Bug description:
  Not sure if this is a bug or a missing feature.

  Current PCB version, v4.3.0-g9dea9f5a, compiled and installed from
  https://github.com/bgamari/geda-pcb

  I also have a previous version 20140316 on different machine.

  My question; how do I re-load a modified .scm to pcb? In the previous
  version simply selecting "Import Schematic"  loads the changes. The
  same operation in the latest version does nothing.

  How are schematic changes re-loaded?

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/2071650/+subscriptions

[Pcb-bugs] [Bug 2071650] [NEW] Import Schematics not working after .scm mod

[Charles B. <20...@bu...>]

Public bug reported:

Not sure if this is a bug or a missing feature.

Current PCB version, v4.3.0-g9dea9f5a, compiled and installed from
https://github.com/bgamari/geda-pcb

I also have a previous version 20140316 on different machine.

My question; how do I re-load a modified .scm to pcb? In the previous
version simply selecting "Import Schematic"  loads the changes. The same
operation in the latest version does nothing.

How are schematic changes re-loaded?

** Affects: pcb
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/2071650

Title:
  Import Schematics not working after .scm mod

Status in pcb:
  New

Bug description:
  Not sure if this is a bug or a missing feature.

  Current PCB version, v4.3.0-g9dea9f5a, compiled and installed from
  https://github.com/bgamari/geda-pcb

  I also have a previous version 20140316 on different machine.

  My question; how do I re-load a modified .scm to pcb? In the previous
  version simply selecting "Import Schematic"  loads the changes. The
  same operation in the latest version does nothing.

  How are schematic changes re-loaded?

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/2071650/+subscriptions

[Pcb-bugs] [Bug 2069801] [NEW] Import Schematics not working or different.

[Charles B. <20...@bu...>]

Public bug reported:

Not sure if this is a bug or a 'feature'.

'Import Schematics' in the File menu in previous version reloaded a
modified .sch file. Import after a modification now does nothing.
Perhaps there is some other method to do the re-import in current
version.

** Affects: pcb
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/2069801

Title:
  Import Schematics not working or different.

Status in pcb:
  New

Bug description:
  Not sure if this is a bug or a 'feature'.

  'Import Schematics' in the File menu in previous version reloaded a
  modified .sch file. Import after a modification now does nothing.
  Perhaps there is some other method to do the re-import in current
  version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/2069801/+subscriptions

[Pcb-bugs] [Bug 1952989] Re: GTK3 User Interface

[Cesar S. <19...@bu...>]

Hi Bert. DJ was kind enough to give me commit access to the main PCB
repository on git.geda-project.org/pcb.git, so I'll push the LP1952989
branch there as well, if you don't mind.

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/1952989

Title:
  GTK3 User Interface

Status in pcb:
  Triaged

Bug description:
  pcb requires a GTK3 User Interface sooner or later.

  This bug report (feature request) is raised to serve as the start of a
  topic branch for development.

  Related development issues and decisions for the GTK3 UI shall be
  discussed in this bug report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/1952989/+subscriptions

[Pcb-bugs] [Bug 1952989] Re: GTK3 User Interface

[Cesar S. <19...@bu...>]

Thanks for merging the pull request!
And thanks for giving me access to the github repository! I guess this means I can commit directly to the topic branch LP1952989, then. I'll leave it to you to review and merge the branch into master, of course.

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/1952989

Title:
  GTK3 User Interface

Status in pcb:
  Triaged

Bug description:
  pcb requires a GTK3 User Interface sooner or later.

  This bug report (feature request) is raised to serve as the start of a
  topic branch for development.

  Related development issues and decisions for the GTK3 UI shall be
  discussed in this bug report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/1952989/+subscriptions

[Pcb-bugs] [Bug 1952989] Re: GTK3 User Interface

[Bert T. <19...@bu...>]

Merged pull request on github in topic branch LP1952989.

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/1952989

Title:
  GTK3 User Interface

Status in pcb:
  Triaged

Bug description:
  pcb requires a GTK3 User Interface sooner or later.

  This bug report (feature request) is raised to serve as the start of a
  topic branch for development.

  Related development issues and decisions for the GTK3 UI shall be
  discussed in this bug report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/1952989/+subscriptions

[Pcb-bugs] [Bug 1952989] Re: GTK3 User Interface

[Cesar S. <19...@bu...>]

I prepared a first set of patches. They simply fix some header file
references. They allow more code to be compiled, to find more places
where fixes are needed.

https://github.com/gEDA-pcb-developers/pcb/pull/1

https://github.com/cestrauss/pcb/tree/LP1952989-fix-header-file-
references

Kindly review, and merge to the branch, if appropriate.

I started with these simpler preparatory tasks, will tackle the
pixbuf/pixmap fixes later.

Meanwhile, please treat my fork
(https://github.com/cestrauss/pcb/tree/LP1952989) as work in progress,
not ready to be merged.

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/1952989

Title:
  GTK3 User Interface

Status in pcb:
  Triaged

Bug description:
  pcb requires a GTK3 User Interface sooner or later.

  This bug report (feature request) is raised to serve as the start of a
  topic branch for development.

  Related development issues and decisions for the GTK3 UI shall be
  discussed in this bug report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/1952989/+subscriptions

[Pcb-bugs] [Bug 1952989] Re: GTK3 User Interface

[Cesar S. <19...@bu...>]

Meanwhile, I did a few trivial fixes to the branch.

https://github.com/gEDA-pcb-
developers/pcb/compare/LP1952989...cestrauss:pcb:LP1952989

https://github.com/cestrauss/pcb/tree/LP1952989

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/1952989

Title:
  GTK3 User Interface

Status in pcb:
  Triaged

Bug description:
  pcb requires a GTK3 User Interface sooner or later.

  This bug report (feature request) is raised to serve as the start of a
  topic branch for development.

  Related development issues and decisions for the GTK3 UI shall be
  discussed in this bug report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/1952989/+subscriptions

[Pcb-bugs] [Bug 1952989] Re: GTK3 User Interface

[Cesar S. <19...@bu...>]

No problem! I'll give it a try.

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/1952989

Title:
  GTK3 User Interface

Status in pcb:
  Triaged

Bug description:
  pcb requires a GTK3 User Interface sooner or later.

  This bug report (feature request) is raised to serve as the start of a
  topic branch for development.

  Related development issues and decisions for the GTK3 UI shall be
  discussed in this bug report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/1952989/+subscriptions

[Pcb-bugs] [Bug 1952989] Re: GTK3 User Interface

[Bert T. <19...@bu...>]

Hi Cesar, I got bogged down in the pixbuf/pixmap stuff, and haven't
found time to dig into the code for a solution. I have pushed all my
commits, no commits or improvements lagging.

-- 
You received this bug notification because you are a member of PCB Bug
Team, which is subscribed to pcb.
https://bugs.launchpad.net/bugs/1952989

Title:
  GTK3 User Interface

Status in pcb:
  Triaged

Bug description:
  pcb requires a GTK3 User Interface sooner or later.

  This bug report (feature request) is raised to serve as the start of a
  topic branch for development.

  Related development issues and decisions for the GTK3 UI shall be
  discussed in this bug report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pcb/+bug/1952989/+subscriptions