On Tuesday 24 June 2008 16:07:18 Ronaldo Nascimento wrote:
Code
self.aboutdialog = gtk.AboutDialog()
self.aboutdialog.set_version('0.0.1')
self.aboutdialog.show()
How do i get the close button to hide the dialog?
thanks
use self.aboutdialog.run() instead of
Is that code snippet of any help?
def set_foreign_key(self, colnum, SQLObject, colname_1, colname_n):
maps a foreign key to a corresponding attribute in the n-table.
colnum is the position of
the column in the treeview (integer), SQLObject is the SQLObject class
the mapped value
The first window (main window) should be gtk.Window, the others should
probably be gtk.Dialog
You create an instance of your dialog and call run()
It's difficult to tell why this happens without seeing the code.
On Wednesday 11 June 2008 14:42:59 Timo wrote:
Hello all, I'm writing a program
pygtk-cheeseshop
IMHO that sort of utils module would add a lot of overhead as most modules are
too specialized. Instead, it would be nice to have some sort of cheese shop
for additional pygtk modules.
One additional problem of those modules or packages is that they often lack
good
According to the docs both the constructor of gtk.ComboBox and
gtk.Combobox.set_model() expect a gtk.TreeModel. However, if I use a custom
model (derived from gtk.GenericTreeModel) I get some strange behaviour.
Instead of showing all rows of the Model it will only show repeatedly the
value of
what platform, which version?
On Monday 02 June 2008 04:49:02 Adiv wrote:
My PyGTK is failing to load. It seems to think it may be missing a
component or something. I have tried reinstalling it, using slightly older
versions, etc, to no avail. It works fine on the laptop, so I don't know
I am working on a package that provides some models for use with SQLObject
(see http://www.sqlobject.org for further details), thus creating database
frontends is made a lot easier.
Internally, the model uses a python list of SQLObject instances.
Now I have bumped into the following:
As long
On Friday 30 May 2008 11:53:58 Casey McGinty wrote:
Hi,
Is there a best coding practice for the best point in the program execution
to initialize secondary PyGtk windows?
For example, all the background windows can be created during program init,
but this might slow down the program
