Re: [pygtk] Inheriting From Widgets

2000-02-25 Thread James Henstridge
In more complex Tkinter projects, that rule does not seem to be followed. Usually you may want to subclass an existing widget to get some special behaviour. In both pygtk and Tkinter cases, subclassing a widget is the easiest way of achieving this. I don't really have any specific recommend

Re: [pygtk] GtkCTree

2000-02-25 Thread Brandt Kurowski
> > The things to pay attention to are the parent/sibling > > relationships, which are explained in the GTK+ API docs. > > You probably got better docs then I do, or understood them better > (I'm using the info files from gtk+-1.2.6) The docs on http://developer.gnome.org/ are the best I've foun

Re: [pygtk] GtkCTree

2000-02-25 Thread Moshe Zadka
On Fri, 25 Feb 2000, Brandt Kurowski wrote: > this is off the top ofmy head, but it should be close to > something functional for creating a GtkCTree: Thanks a lot. > The things to pay attention to are the parent/sibling > relationships, which are explained in the GTK+ API docs. You probably g

Re: [pygtk] GtkCTree

2000-02-25 Thread Brandt Kurowski
On Fri, Feb 25, 2000 at 08:59:15PM +0200, Moshe Zadka wrote: > I've been trying to play a bit with GtkCTree, and I can't seem > to get anything useful out of it. Does anyone have small > sample code which displays a GtkCTree? this is off the top of my head, but it should be close to something fun

[pygtk] timeout causes lockup?

2000-02-25 Thread lists
After a call to a timeout, which does gtk calls and network calls, my application locks up. Any ideas?? thanks, - Scott To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]

[pygtk] GtkCTree

2000-02-25 Thread Moshe Zadka
I've been trying to play a bit with GtkCTree, and I can't seem to get anything useful out of it. Does anyone have small sample code which displays a GtkCTree? Thanks. -- Moshe Zadka <[EMAIL PROTECTED]>. INTERNET: Learn what you know. Share what you don't. To unsubscribe: echo "unsubscribe" | ma

Re: [pygtk] "Modal" File Dialog

2000-02-25 Thread Aaron Optimizer Digulla
On Fri, Feb 25, 2000 at 03:56:10PM +0200, Moshe Zadka wrote: > > > This maybe slightly off-topic, since it's more about UI design then about > > > PyGTK specifically, but the alternative I'm considering is to make > > > it into a dialog which replaces an entry field. Is that considered all > > >

Re: [pygtk] "Modal" File Dialog

2000-02-25 Thread Moshe Zadka
On Fri, 25 Feb 2000, Aaron Optimizer Digulla wrote: > On Fri, Feb 25, 2000 at 01:41:04PM +0200, Moshe Zadka wrote: > > > This maybe slightly off-topic, since it's more about UI design then about > > PyGTK specifically, but the alternative I'm considering is to make > > it into a dialog which rep

Re: [pygtk] "Modal" File Dialog

2000-02-25 Thread Moshe Zadka
On Fri, 25 Feb 2000, James Henstridge wrote: > If there is part of the GUI that the user shouldn't use while the dialog > is open, consider making it insensitive (with set_sensitive(FALSE)).This > is sometimes nicer than making a window application modal. Dang! That's a good idea, I'm sorry I d

[pygtk] Inheriting From Widgets

2000-02-25 Thread Moshe Zadka
My previous experience in Python GUI toolkits was with Tkinter. In Tkinter, the official advice was ``don't inherit from anything except Frame''. I wonder what the official advice about PyGTK is. Is it considered politically correct to inherit from Gtk[VH]Box? Are there any caveats? Thanks in

Re: [pygtk] "Modal" File Dialog

2000-02-25 Thread James Henstridge
If there is part of the GUI that the user shouldn't use while the dialog is open, consider making it insensitive (with set_sensitive(FALSE)). This is sometimes nicer than making a window application modal. James. -- Email: [EMAIL PROTECTED] WWW: http://www.daa.com.au/~james/ On Fri, 25 Feb

Re: [pygtk] "Modal" File Dialog

2000-02-25 Thread Aaron Optimizer Digulla
On Fri, Feb 25, 2000 at 01:41:04PM +0200, Moshe Zadka wrote: > > Unless you really have to it is probably better not to use a modal dialog, > > as most users prefer non modal dialogs. > This maybe slightly off-topic, since it's more about UI design then about > PyGTK specifically, but the alterna

Re: [pygtk] "Modal" File Dialog

2000-02-25 Thread Moshe Zadka
On Fri, 25 Feb 2000, James Henstridge wrote: > You can use the set_modal method of any GtkWindow derived class: > window.set_modal(TRUE) Thanks. > Unless you really have to it is probably better not to use a modal dialog, > as most users prefer non modal dialogs. This maybe slightly off-topic,

Re: [pygtk] "Modal" File Dialog

2000-02-25 Thread Aaron Optimizer Digulla
On Fri, Feb 25, 2000 at 12:21:04PM +0200, Moshe Zadka wrote: > > >[...how to create a modal file requester...] > > This sounds like "I want to annoy the user". Why do you want it > > modal ? > The main application window is all kinds of bells and whistles, among > which is a place to fill in a fi

Re: [pygtk] "Modal" File Dialog

2000-02-25 Thread James Henstridge
You can use the set_modal method of any GtkWindow derived class: window.set_modal(TRUE) When the dialog is shown, it will act as any other dialog, but no other window can take input. It will loose modality when it is hidden or destroyed. Unless you really have to it is probably better not to

Re: [pygtk] "Modal" File Dialog

2000-02-25 Thread Moshe Zadka
On Fri, 25 Feb 2000, Aaron Optimizer Digulla wrote: > On Fri, Feb 25, 2000 at 09:41:45AM +0200, Moshe Zadka wrote: > > > It's probably extremely easy, but I'm having problems figuring > > out how to display a file dialog so when it's active, the rest of > > the application doesn't respond. > > D

Re: [pygtk] "Modal" File Dialog

2000-02-25 Thread Aaron Optimizer Digulla
On Fri, Feb 25, 2000 at 09:41:45AM +0200, Moshe Zadka wrote: > It's probably extremely easy, but I'm having problems figuring > out how to display a file dialog so when it's active, the rest of > the application doesn't respond. > Do I need a seperate event loop, or something like that? This sou

Re: [pygtk] I am pissed off

2000-02-25 Thread Frederic Gobry
> Now when I try to use any of the menu stuff it segfaults without > explanation. Happy to see I'm not the only one ;-) I guess there is really a bug, it's not in your code. But as far as I remember, the stack at crash time does not point into pygnome, so if there is a bug in it, it appears with