On Wed, Dec 12, 2007 at 10:53:48PM -0700, Jason Creighton wrote:
On Wed, Dec 12, 2007 at 08:12:35PM -0800, Andrew Sackville-West wrote:
On Wed, Dec 12, 2007 at 05:35:16PM -0800, codesite-noreply@google.com wrote:
This gets us in trouble with Gnucash, which, for some reason, sends, one after the other, a MapRequest, a synthetic UnmapNotify and then another MapRequest.
I've said this before, but it bears repeating: this looks an awful lot like Gnucash is doing something wrong. Why would some dialogs but not others generate this behavior? It must be something internal to gnucash that is broken or at least odd. GNucash only fairly recently completed the transtion to gtk2.0 and it's likely that some problems exist.
Well, it's odd that Gnucash does that, but I don't think it's broken: Mapping, unmapping and then remapping a window *should* leave it visible, and the fact that it didn't in xmonad was a bug, which we fixed.
turns out that dialog gtk_widget_show_all's to get all the widgets visible, hides the dialog, tweaks what is ultimately visible and then reshows it. perfectly reasonable behavior in the absence of gtk_widget_show_all_children(), I guess. meanwhile, commenting out the gtk_widget_hide makes a very usable dialog, IMO. thanks again for the attention on this. A