Cannot move selection

[Bert Timmerman]

Reported on the geda-user mailing list:

I have this small little test thing

http://turkos.aspodata.se/tmp/tz.pcb

I select all visable objects and try to move it, but pcb only allows
me to move it down or to the right.

How do I do to move it up, have anyone experienced something lika that?

///

$ pcb --version
Warning: Actions not found: Quit
PCB version v4.0.2-g7faad273

configured with:
./configure --with-gui=lesstif --disable-dbus --disable-png \
 --with-exporters="bom gerber ps ipcd356" --disable-doc \
 --with-included-gettext

BTW, what is this Warning about, I get millions (460) of thoose
every time I start pcb.

Regards,
/Karl Hammar

-----------------------------------------------------------------------
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
[phone]

[Bert Timmerman (bert-timmerman)]

Karl:
> > I have this small little test thing
> >
> > http://turkos.aspodata.se/tmp/tz.pcb
> >
> > I select all visable objects and try to move it, but pcb only allows
> > me to move it down or to the right.
> >
> > How do I do to move it up, have anyone experienced something lika that?
 Ok, tested and found theese commits:
f79c6f8a3c53df61e1d139ba8b6e264fbbfa28c3 is bad
2d695f8b7c0ed90b99888f2424ad7449f7c3f0d5 is good

Regards,
/Karl Hammar

-----------------------------------------------------------------------
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
[phone]

[Bert Timmerman (bert-timmerman)]

Hi Karl,

Happy new year and best wishes for 2018.

Thank you for your report and test file, and pointing to good and bad commits.

I confirm this bug and have reproduced in both gtk and lesstif UIs in "master" (== devel).

A quick check gives that this bug doesn't occur in pcb-4.0.2 (== stable).

I (we) will shortly look further into it.

This will have to be resolved before the release of pcb-4.1.0 (== show stopper).

Kind regards,

Bert Timmeman.

[Bert Timmerman (bert-timmerman)]

Hi,

Resolved by reverting the commits:

683b191cd7cecb388609fffbb519ab1484fbb005

and

f79c6f8a3c53df61e1d139ba8b6e264fbbfa28c3

Kind regards,

Bert Timmerman.

[Chad Parker (parker-charles)]

I found the problem in the original commit. There's a fix in branch LP1744589.