Not that I know of, although I have seen Python scripts out there that do it for you.

Joono,

What sort of validation are you looking for?

It seems to me there is a lot of code blocks that could be auto-generated for all the default events and such. Are there any developments ‘out there’ that pull Python and Glade together into one development environment (IDE)?

Keep up the great work, I’ll be back!

Thanks for the semi-colon catch! I’ve spent way too much time using C++!

Also thanks for the kind words!

Thanks for the information and the great tip! If you want to take a loot at more Tree processing take a look at the PyLan tutorials as I do a little bit more in there.

For plotting you might want to take a look at Matplotlib

I will take a look into the rubber banding, that’s an interesting feature that I have not looked into yet.

I found that I wanted to double-click the entries to edit them.

To do it, I added a handler for the row_activated event using glade (which was just what I wanted) and called the event on_EditRow. Turns out that row_activated gives more arguments that specify what was selected (oddly enough), but I wasn’t sure how to use them so I just wrapped them up and called your existing on_EditWine function.

So I added the handler to the dictionary with a

“on_EditRow” : self.on_EditRow

in the middle there, then wrote the wrapper,

def on_EditRow(self, widget, path, column):
“”" Called when the user double-clicks a row “”"
self.on_EditWine(widget)

Since the double-clicked row is also selected, it’s just a little extra work that could be avoided in the on_EditWine function but it doesn’t hurt (I don’t think).

Anyway, keep up the good tutorials. I just found your site and have been learning a bunch.

(Any thoughts on a widget I could embed that would do 2-D plots of data? Ideally, I just pass it a couple of data sets and it does all the hard work of plotting.)

(One more, how about a tutorial about rubber-banding items? It’s integral to the GUI experience and used extensively, but there seem to be a fair amount of complexity in both the graphical part and using the bounding box for item selection that I’ve never seen one.)

Thanks for the great catch!

I figured out the problem, it’s what I’ve heard referred to as a “sticky-variable” problem in the past, which means that it’s simply a code error.

The problem is in these lines in the windDialog class:

#They have passed a wine object
self.wine = wine

What this does is set self.wine to be a reference to wine (a shallow copy), so when we change self.wine we are also changing wine itself. So even if we cancel the operation, wine (which is stored in the list) gets changed.

To fix this you can use the following code instead of the above lines:

#They have passed a wine object
self.wine = Wine(wine.wine
					, wine.winery
					, wine.grape
					, wine.year)

This will create a copy of the wine object in self.wine, and stop the cancel problem from happening.