Quoting Mitch Chapman [EMAIL PROTECTED]:
If dragdrop wasn't so complicated in Gtk (=not much docs), I'd
suggest a band of previews which you can drag into two view
areas. If there are lots of previews, the app should provide
a "Hide Large View" toggle so they can switch between "band
On Tue, Aug 01, 2000 at 06:06:14AM -0600, Mitch Chapman wrote:
Well-put, but my customer wants mode*less* dialogs.
They want to be able to continue working with the main
application after the dialog appears.
Oops :-)
Here's the problem scenario: The user has clicked on a
thumbnail and
On Wed, Jul 26, 2000 at 11:35:30AM -0600, Mitch Chapman wrote:
It may be that I'm solving the wrong problem. In other words,
there may be a better way to present the information that's
currently being displayed in these modeless dialogs. But if
y'all have any suggestions for how to solve
On Tue, 1 Aug 2000, Mitch Chapman wrote:
Well-put, but my customer wants mode*less* dialogs.
They want to be able to continue working with the main
application after the dialog appears.
Imagine a window full of thumbnail vector images. A single
left-click on a thumbnail brings up a
I'm not sure where to ask this, so will bug you all. :)
I'm working on a pygtk application which has a main window and
several modeless dialogs. The customer has requested that the
modeless dialogs always stay in front of the main window, but that
they be separately iconifiable. (The dialogs
On Wed, 26 Jul 2000, Mitch Chapman wrote:
I'm not sure where to ask this, so will bug you all. :)
I'm working on a pygtk application which has a main window and
several modeless dialogs. The customer has requested that the
modeless dialogs always stay in front of the main window, but
