[PythonCAD] New patches to PythonCAD . . . .

Art Haas ahaas at airmail.net
Mon Dec 19 22:42:21 CET 2005

On Tue, Dec 20, 2005 at 09:58:37AM +1300, Wilbert Knol wrote:
> On Saturday 17 December 2005 06:04, Art Haas wrote:
> > I played with changing mirroring operations to work in both 'select
> > then act' and 'act then select'
> <snip>
> > Let me get some feedback on this
> Great! A nice refinement. It works both ways - seamlessly.
> An observation: if the program were in 'select mode' when idle, then 
> the 'select then act' way would be even quicker, but this may not be 
> so easily coded.

I don't know. Some coding or patches might shed light on the level of
difficulty as well as any performance or useability issues.

> > Index: PythonCAD/Interface/Gtk/gtkmirror.py
> > ===================================================================
> > --- PythonCAD/Interface/Gtk/gtkmirror.py	(revision 2102)
> > +++ PythonCAD/Interface/Gtk/gtkmirror.py	(working copy)
> If I apply this (and other) patches, would that confuse future svn 
> updates? 

The mirroring patches are checked in now, as well as a new patch that
tries to make PythonCAD better handler key-press events when you are
using a tool that accepts keyboard entry but the focus - the widget that
will respond to the keyboard - is not the entry widget at the bottom of
the screen.

> Or should I reverse any patches before doing an 'svn update'?  I've 
> been doing the latter, but I  see my program produces 'SDB Debug' on 
> stdout. Perhaps the SDB code has been committed to repo.

In some place the "SDB Debug" is in. The easiest thing to do if you want
to check your repo is use 'svn status'. Any files that differ from what
I've checked in will be printed out. As for reversing patches prior to
'svn update', it probably is not a bad idea as you'll avoid any merge
issues. You can always reapply the patch after the update completes.
> Another question: should I do:
>     su -c "python setup.py install"
> following svn updates?

That's up to you. You can always run PythonCAD by invoking the
'gtkpycad.py' script in your checked out copy of the repo, and the code
in the repo will be used as Python's 'sys.path' variable typically
starts looking for files from 'import' in your current directory.
I'd suggest running PythonCAD in this manner if you want to use the
latest stuff, that way the code in Python's installed 'site-packages'
directory is untouched if the current code has problems. The installed
version ends up being a fallback if the development code has problems.

Man once surrendering his reason, has no remaining guard against absurdities
the most monstrous, and like a ship without rudder, is the sport of every wind.

-Thomas Jefferson to James Smith, 1822

More information about the PythonCAD mailing list