Re: gEDA-user: pcb 20070912 and GTK trouble + another bug?
On Mon, 10 Dec 2007, Peter Clifton wrote: On Mon, 2007-12-10 at 07:13 +0100, Igor2 wrote: I hope this bug-reporting and testing is all against the latest CVS version.. as many of the bugs with GTK hid + 20070912 have been fixed there. yup, latest CVS by the time of the patch creation; btw now i can't see the red wireframe helpers while i'm drawing a line (latest CVS). I am not yet sure whether it's related to my local changes but i will test. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb 20070912 and GTK trouble + another bug?
On Mon, 2007-12-10 at 15:23 +0100, Igor2 wrote: On Mon, 10 Dec 2007, Peter Clifton wrote: On Mon, 2007-12-10 at 07:13 +0100, Igor2 wrote: I hope this bug-reporting and testing is all against the latest CVS version.. as many of the bugs with GTK hid + 20070912 have been fixed there. yup, latest CVS by the time of the patch creation; btw now i can't see the red wireframe helpers while i'm drawing a line (latest CVS). I am not yet sure whether it's related to my local changes but i will test. I believe my (unapplied) patch was this one attached. (Need to strip out the dpatch headers). I think we came to the conclusion that there may be two pieces of code attempting to bounds-check / reset the position of the board as the cursor leaves it. We only really need one! NB.. most of the nasty issues only showed up on the backside / flipside of the board. Peter -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) 06_fix_crosshair.dpatch Description: application/shellscript ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb 20070912 and GTK trouble
Stefan Salewski wrote: It is nearly impossible to grab the reference designators OK, this seems to be only a problem if the board is freshly generated by gsch2pcb (and elements dispersed with Disperse all Elements). If I save this board to disk and reopen it, I can move reference designators without problems! Now we should try to find the reason for the jumping window content. Best regards Stefan Salewski ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb 20070912 and GTK trouble
Stefan Salewski wrote: Now we should try to find the reason for the jumping window content. I will try to describe this bug more detailed: The jump of the inner display occurs, when the mouse pointer touches the border of the inner drawing area. It is not related to the sliders (at right and bottom of the window, for panning.) Jump occurs also when I move the mousepointer to the top window limit, beside the pulldown menu, where no action element is located. The displayed area changed, and the coordinates displayed in the upper window border reflect this position change. If I press the right mouse button and do a minimal mouse movement (minimal panning) the window content and the position display jumps back to the correct value. If I use the middle mouse wheel to change zoom, display will not jump back to correct position. The jump occurs if the pcb window is maximized or smaller. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb 20070912 and GTK trouble
On Sun, Dec 09, 2007 at 01:41:10PM +0100, Stefan Salewski wrote: Now we should try to find the reason for the jumping window content. I was messing around in the gtk hid making a (long!) list of issues and one critical one I hit involved toggling layer visibility from a torn-off 'shown layers' menu. The gtk interface code goes into a loop where the updating of checked-ness triggers callbacks (a problem solved in Xt 20 years ago!). There's all kinds of gross avoid-reentry code in the gtk hid, but some of the callbacks seem to get deferred and originate from 'main' again. Those callbacks can form an infinite loop. I bet some of the scrolling madness is caused by interacting updates like that. -- Ben Jackson AD7GD [EMAIL PROTECTED] http://www.ben.com/ ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb 20070912 and GTK trouble
On Sun, Dec 09, 2007 at 08:42:26PM +0100, Stefan Salewski wrote: If I press the right mouse button and do a minimal mouse movement (minimal panning) the window content and the position display jumps back to the correct value. ...and you have to do that to 're prime' so you can get the jump again. (btw, is the right-button-pans behavior of GTK some kind of GTK standard? I think the right=rotate, middle=pan of lesstif is much more common of other similar applications) -- Ben Jackson AD7GD [EMAIL PROTECTED] http://www.ben.com/ ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb 20070912 and GTK trouble
(btw, is the right-button-pans behavior of GTK some kind of GTK standard? It's supposed to be right=popup though. I put pan on middle because that's also the scroll wheel, so all navigation is on one button - less change of accidental mis-mousing. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb 20070912 and GTK trouble
On Sun, 9 Dec 2007, Stefan Salewski wrote: Stefan Salewski wrote: Now we should try to find the reason for the jumping window content. I will try to describe this bug more detailed: The jump of the inner display occurs, when the mouse pointer touches the border of the inner drawing area. It is not related to the sliders (at right and bottom of the window, for panning.) Jump occurs also when I move the mousepointer to the top window limit, beside the pulldown menu, where no action element is located. The displayed area changed, and the coordinates displayed in the upper window border reflect this position change. If I press the right mouse button and do a minimal mouse movement (minimal panning) the window content and the position display jumps back to the correct value. If I use the middle mouse wheel to change zoom, display will not jump back to correct position. The jump occurs if the pcb window is maximized or smaller. I've spent a few hours debugging this. I've submitted a bugreport on sf (http://sourceforge.net/tracker/index.php?func=detailaid=1840422group_id=73743atid=538811) I've found that the bug is related to grid and grid snapping code and also depends on what's the grid offset compared to the drawing area is. Please see the comments in the bugreport. I've also submitted a patch there (and a notify about this on de geda-dev list) that partially fixes this bug and probably a number of other bugs that may happen when PCB wants to scroll somwhere to show something to the user (DRC?). The patch won't stop PCB to jump away, but once it has jumped away, at least it stays there so next time you pan/scroll/zoom/click it won't jump back to the previous position. This is not a workaround - the patch replaces a FIXME in the code. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb 20070912 and GTK trouble
Is this similar to the lesstif bug I fixed a while ago, where grid snapping causes the crosshair to leave the window? ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb 20070912 and GTK trouble
On Mon, Dec 10, 2007 at 05:53:38AM +0100, Igor2 wrote: I've spent a few hours debugging this. I've submitted a bugreport on sf (http://sourceforge.net/tracker/index.php?func=detailaid=1840422group_id=73743atid=538811) I've found that the bug is related to grid and grid snapping code and also depends on what's the grid offset compared to the drawing area is. Please see the comments in the bugreport. If you mean 'pcb-gtk-pan.patch' I just applied that and I can still reproduce the jumping. It might even be worse. I set the grid to 100mil and zoomed way in and it jumps every time I mouse out of the work area, basically. It's almost like an auto-scroll? Also, I get two new assertions at startup: (pcb:24707): Gtk-CRITICAL **: gtk_range_set_value: assertion `GTK_IS_RANGE (range)' failed (pcb:24707): Gtk-CRITICAL **: gtk_range_set_value: assertion `GTK_IS_RANGE (range)' failed Actually last night I tried the gtk hid and I found much worse bugs than this (eg spinning forever in menu callbacks) which made me think that the GTK hid was not just a few bandaids away from usable. -- Ben Jackson AD7GD [EMAIL PROTECTED] http://www.ben.com/ ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: pcb-20070912 problems
People, I'm running the cvs/lesstif version of pcb-20070912 (because the download version won't start properly). I'm having problems with the commands not displaying results fully. For example the commands Connects - Optomize ratsnest will display ratsnest information on the first request; subsequest requests appear to execute, but no information is ever displayed. Connects - Lookup connection to object has similiar problems; requests appear to execute, however no information is ever displayed. In fact ths situation is at the point where I'm thinking of re-installing pcb-200702?? mostly because the gtk version seems to work properly. Any comments/help would be appreciated. Harold Skank ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb-20070912 problems
Is it just a matter of the scroll bars defaulting to the right side, instead of the left? If so, I've fixed that. Have you tried the CVS version of pcb? ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: PCB 20070912 surprising silk behavior
Are you sure you're not drawing on the back copper layer? It all seems to work OK for me. Note that you swap silk layers by using the TAB key, not by selecting a different layer. Both silk layers should be the same color. Also, silk lines won't clear polygons even when that flag is set. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: PCB 20070912 surprising silk behavior
On Mon, 2007-11-26 at 22:02 -0500, DJ Delorie wrote: Huh. Works fine here, but I'm using cvs on FC6. I'm sure I've seen that bug before, but I can't recall how / why it was triggered. It may have been fixed in CVS. Peter C. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb-20070912
Helo How compile pcb for FreeBSD? Sorry my English :( Igor ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb-20070912
On Sunday 30 September 2007 16:05:00 Igor Černý wrote: Helo How compile pcb for FreeBSD? It should Just Work: ./configure make The configure script should tell you if you have any required development libraries missing. If you have any specific problems, please let us know. Peter -- Peter Brett Electronic Systems Engineer Integral Informatics Ltd signature.asc Description: This is a digitally signed message part. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb-20070912
On 9/14/07, Peter Clifton wrote: Out of interest, what distribution are you using this with - the only distro where I've seen mixed 32 / 64 bit binaries is OpenSUSE (because the servers at Engineering are mostly 64 bit machines running OpenSUSE 10.2). Fedora does have multilibs support as well. Chitlesh -- http://clunixchit.blogspot.com ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb-20070912
--- Dan McMahill wrote:
You should be nervous.
Yes, I am. BTW,
Index: parse_y.y
===
RCS file: /cvsroot/pcb/pcb/src/parse_y.y,v
retrieving revision 1.40
diff -U1 -b -r1.40 parse_y.y
--- parse_y.y 21 Apr 2007 21:21:55 - 1.40
+++ parse_y.y 17 Sep 2007 06:01:10 -
@@ -1018,3 +1018,3 @@
{
- CreateNewArcOnLayer(Layer, $3*100, $4*100,
$4*100, $5*100, $9, $10,
+ CreateNewArcOnLayer(Layer, $3*100, $4*100,
$5*100, $5*100, $9, $10,
$7*100, $8*100,
OldFlags($11));
, please.
I suspect there is a lot broken about
diagonal pads
Nack. essentially DRC and gdlib output. I don't mention autorouter, because the
changes needed are evident there.
P.S.
Index: hid/gtk/gui-top-window.c
===
RCS file: /cvsroot/pcb/pcb/src/hid/gtk/gui-top-window.c,v
retrieving revision 1.45
diff -U2 -b -r1.45 gui-top-window.c
--- hid/gtk/gui-top-window.c17 Aug 2007 03:51:25 - 1.45
+++ hid/gtk/gui-top-window.c17 Sep 2007 06:06:52 -
@@ -3699,6 +3699,4 @@
filename = 0;
- free (home_pcbmenu);
-
bir = resource_parse (0, gpcb_menu_default);
if (!bir)
@@ -3711,4 +3709,6 @@
r = resource_parse (filename, 0);
+ free (home_pcbmenu);
+
if (!r)
r = bir;
and
Index: misc.c
===
RCS file: /cvsroot/pcb/pcb/src/misc.c,v
retrieving revision 1.65
diff -U2 -b -r1.65 misc.c
--- misc.c 1 Aug 2007 02:49:53 - 1.65
+++ misc.c 17 Sep 2007 06:04:26 -
@@ -812,12 +812,5 @@
QuitApplication (void)
{
- /*
- * save data if necessary. It not needed, then don't trigger EmergencySave
- * via our atexit() registering of EmergencySave(). We presumeably wanted
to
- * exit here and thus it is not an emergency.
- */
- if (PCB-Changed Settings.SaveInTMP)
-EmergencySave ();
- else
+ /* the data are not to be emergencysaved */
DisableEmergencySave ();
___
Want ideas for reducing your carbon footprint? Visit Yahoo! For Good
http://uk.promotions.yahoo.com/forgood/environment.html
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb-20070912
This isn't the problem I reported a while back is it? Fedora 7 comes with automake 1.10 and doesn't include aclocal-1.9. Configure apparently runs ok and you can miss the error message when you run make. I ran autogen.sh first, and then everything is happy. On Fri, 2007-09-14 at 17:30 +0100, Peter Clifton wrote: On Fri, 2007-09-14 at 09:52 -0500, Harold D. Skank wrote: Dan, I've awaited this release for some time now, as I've been having difficulty with some polygon issues on a large design. However, following download, I was some surprised that I could not get the file to compile. I should mention that I'm running Fedora-7 on an AMD-64, and I was attempting to compile in the 32-bit mode to avoid some operational issues that I have faced. I could run: CFLAGS='m32 ./configure --with-hid=gtk however a subsequent make command responded as though configure had not completed. In the end I had to go back to pcb-20070208. -- Peter Baxendale [EMAIL PROTECTED] ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb-20070912
On Sat, 15 Sep 2007 22:21:30 -0400 Dan McMahill [EMAIL PROTECTED] wrote: When I call the command window with ':', it appears without the text entry field (Dropdown and Close buttons are there). When I press the dropdown button, _crash_ - pcb disappears! John wierd. I'm not able to reproduce this. I get the entry and no crash. Which GUI are you using? Lesstif or Gtk? What happens if you go into the preferences-general tab and turn off the separate command window option? Can you get a back trace on the crash? Hi Dan. Another day, no more crashes. I'll try more later today. Maybe they appear after a while of usage (as they did they other day). There are a few suspicious messages I hadn't seen because I normally don't call PCB from a terminal. 1) When opening the 'Open file' dialog, I get four times: *** attempt to put segment in horiz list twice 2) When toggling the unit button, I get (not the first time): (pcb:20034): Gtk-CRITICAL **: gtk_toggle_action_set_active: assertion `GTK_IS_TOGGLE_ACTION (action)' failed handle_grid_units_change() get_grid_value_index() get_grid_value_index() (pcb:20034): Gtk-CRITICAL **: gtk_toggle_action_set_active: assertion `GTK_IS_TOGGLE_ACTION (action)' failed I'll try to re-crash this evening. Thanks, John ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb-20070912
On Wed, 12 Sep 2007 23:25:20 -0400 Dan McMahill [EMAIL PROTECTED] wrote: I just uploaded a new pcb snapshot to the sourceforge download area. My goal is to make the next one in closer to 3 months from now instead of having a 7 month gap like this last time. Wow... A big one. When I call the command window with ':', it appears without the text entry field (Dropdown and Close buttons are there). When I press the dropdown button, _crash_ - pcb disappears! John ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb-20070912
John Coppens wrote: On Wed, 12 Sep 2007 23:25:20 -0400 Dan McMahill [EMAIL PROTECTED] wrote: I just uploaded a new pcb snapshot to the sourceforge download area. My goal is to make the next one in closer to 3 months from now instead of having a 7 month gap like this last time. Wow... A big one. When I call the command window with ':', it appears without the text entry field (Dropdown and Close buttons are there). When I press the dropdown button, _crash_ - pcb disappears! John wierd. I'm not able to reproduce this. I get the entry and no crash. Which GUI are you using? Lesstif or Gtk? What happens if you go into the preferences-general tab and turn off the separate command window option? Can you get a back trace on the crash? If you have a build lying around, cd pcb-20070912/src ./pcbtest.sh -gdb gdb run do the stuff to make it crash and then gdb bt -Dan ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb-20070912
Ineiev wrote: =Ben Jackson wrote: DRC for square pads is not fixed. I'm sorry. Is there a sf tracker bug for this? It was filed approximately three nights ago (request ID 1791388). however this is a well-known misfeature. it was spoken about in this list some two months ago. =Dan McMahill wrote: Can you be more specific as to what is still broken? I'm fairly certain that what I fixed was the calculation of minimum distance between two rectangular pads. I think the calculation was correct on that moment, but somewhere in April diagonal pads were enabled. this broke DRC again (i.e. for diagonal rectangular pads). maybe this is not very important. I really don't know why I am so anxious about this. ah. You should be nervous. I suspect there is a lot broken about diagonal pads which is why I never enabled them before. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb-20070912
I just uploaded a new pcb snapshot to the sourceforge download area. My goal is to make the next one in closer to 3 months from now instead of having a 7 month gap like this last time. Thank you. Good work. But should you have written Fix DRC checking of square pads to square pads? DRC for square pads is not fixed. I'm sorry. ___ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb-20070912
On Thu, Sep 13, 2007 at 11:34:44AM +0100, Ineiev wrote: But should you have written Fix DRC checking of square pads to square pads? DRC for square pads is not fixed. I'm sorry. Is there a sf tracker bug for this? -- Ben Jackson AD7GD [EMAIL PROTECTED] http://www.ben.com/ ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb-20070912
Ineiev wrote: I just uploaded a new pcb snapshot to the sourceforge download area. My goal is to make the next one in closer to 3 months from now instead of having a 7 month gap like this last time. Thank you. Good work. But should you have written Fix DRC checking of square pads to square pads? DRC for square pads is not fixed. I'm sorry. Can you be more specific as to what is still broken? I'm fairly certain that what I fixed was the calculation of minimum distance between two rectangular pads. It used to be the case that one pad was increased in size by bloat in both x and y and then checked to see if it overlapped the other pad. That of course means you increased by sqrt(2)*bloat in the diagonal direction. That is the aspect which was (or should have been) fixed. -Dan ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb-20070912
=Ben Jackson wrote: DRC for square pads is not fixed. I'm sorry. Is there a sf tracker bug for this? It was filed approximately three nights ago (request ID 1791388). however this is a well-known misfeature. it was spoken about in this list some two months ago. =Dan McMahill wrote: Can you be more specific as to what is still broken? I'm fairly certain that what I fixed was the calculation of minimum distance between two rectangular pads. I think the calculation was correct on that moment, but somewhere in April diagonal pads were enabled. this broke DRC again (i.e. for diagonal rectangular pads). maybe this is not very important. I really don't know why I am so anxious about this. ___ Want ideas for reducing your carbon footprint? Visit Yahoo! For Good http://uk.promotions.yahoo.com/forgood/environment.html ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: pcb-20070912
I just uploaded a new pcb snapshot to the sourceforge download area. My goal is to make the next one in closer to 3 months from now instead of having a 7 month gap like this last time. Release Notes for PCB snapshot 20070912 This release represents nearly 200 commits and as such this summary clearly is not complete. See the ChangeLog file for the complete list of changes. - Many many bug fixes. Too many to list. - Added keystone, CK, Nichicon, and Optek footprint libraries - Add attribute editor to the GTK HID - Add a fileselect() function to the HID spec - Fix ps output with drill helper on - Add a visual indicater when elements are locked - Corrections to the manual - BOM can export in mm as well as mil - Fix a ps output bug with arcs - Fix some memory leaks found with Coverity - Added autoconf test for buggy versions of m4 - Fixed some footprint drill sizes - Add user customizable menus for the gtk HID. The gtk HID now is capable of reading the same format menu resource files as the lesstif HID. This represents significant rework of the menu code and menu callback code. - Added Center() action - Store the file format in the .pcb file. This will let pcb know when presented with a file which is too new. The code for checking the format was present in the prior snapshot. - Fix DRC checking of square pads to square pads - Added window panning/cursor warping - Add the ability to directly load a footprint from a file as if it were a complete layout. - Add a Popup() action Have fun. -Dan ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
