Mmmm... what I need is a place to put some informations about the image which is currently being displayed by a GtkImage in the main HildonWindow. With the version of mrawviewer currently in extras-testing I did that by painting directly over the image itself, as it is always resized to fit the screen.<br>
With the next version I've introduced the possibility to zoom in / out, and I wanted the image informations to remain visible all the time while zooming and scrolling around the image, that's why I thought about a see-through-GtkWindow positioned over the underlying image.<br>
Of course that window must stay around until the user explicitly closes it by toggling a filter in the HildonAppMenu. It can't be moved nor resized nor it gets any focus, it's only purpose is displaying some informations.<br>
<br>I'll investigate on how can I make the transparent window a child of the main HildonAppWindow upon its creation as you suggested.<br><br>Thanks, <br><br>--<br>Luca Donaggio<br><br><div class="gmail_quote">2009/11/13 Kimmo Hämäläinen <span dir="ltr"><<a href="mailto:kimmo.hamalainen@nokia.com">kimmo.hamalainen@nokia.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Fri, 2009-11-13 at 10:44 +0100, Hamalainen Kimmo (Nokia-D/Helsinki)<br>
wrote:<br>
<div class="im">> On Thu, 2009-11-12 at 17:21 +0100, ext Luca Donaggio wrote:<br>
> > Thanks a lot Kimmo!<br>
> ><br>
> > At least, now I know what's happening!<br>
> > Now, what to do to solve the problem? If HildonAppMenu behaves like<br>
> > this by design (and if the bug regards only the fact that it is first<br>
> > mapped and then unmapped while it shouldn't be mapped at all), is<br>
> > there a way to create a floating top level widget on top of a<br>
> > HildonWindow or it is somewhat forbidden by the actual implementation?<br>
> > I don't want to continue the development in the wrong direction, maybe<br>
> > it's better if I stop here and redisign my app to not include the<br>
> > "offending" widget and find another way to present the same<br>
> > informations to the user - but let me say that I grew somewhat fond of<br>
> > my transparent-overlayed-unobtrusive-image-details-window!<br>
><br>
> I think the cleanest (and most risk-free) solution is that you create<br>
> the transparent window as a child window of the main window right from<br>
> the beginning. But I'm not sure how Gtk allows that. Better solution<br>
> would be fixing the WM so that it allows rgba in dialogs, but that can<br>
> be more work...<br>
<br>
</div>I checked the WM support: it seems to be just a matter of commenting out<br>
the offending code in mb-wm-client.c. But if you use a dialog, your<br>
dialog is closed before you can access the application menu, which is<br>
probably what you are trying to do.<br>
<font color="#888888"><br>
-Kimmo<br>
</font><div><div></div><div class="h5"><br>
><br>
> -Kimmo<br>
><br>
> ><br>
> > What do you think?<br>
> ><br>
> > --<br>
> > Luca Donaggio<br>
> ><br>
> > 2009/11/11 Kimmo Hämäläinen <<a href="mailto:kimmo.hamalainen@nokia.com">kimmo.hamalainen@nokia.com</a>><br>
> > On Wed, 2009-11-11 at 08:28 +0100, Hamalainen Kimmo (Nokia-<br>
> > D/Helsinki)<br>
> > wrote:<br>
> > > On Tue, 2009-11-10 at 16:15 +0100, ext Luca Donaggio wrote:<br>
> > > > I thought it was somewhat related to transparency because<br>
> > doing this:<br>
> > > ><br>
> > > > gdk_window_reparent(win->window,gtk_widget_get_window<br>
> > (GTK_WIDGET<br>
> > > > (mainwin)),300,200);<br>
> > > ><br>
> > > > makes the HildonAppMenu work again at the price of loosing<br>
> > the<br>
> > > > transparency effect (modified code attached).<br>
> > ><br>
> > > Reparenting 'win->window' makes it a child of 'mainwin'.<br>
> > That is<br>
> > > completely different ballgame than the original code, which<br>
> > keeps 'win-<br>
> > > >window' a top-level window (child of the root). When the<br>
> > window is not<br>
> > > top-level, it's not managed by the window manager anymore,<br>
> > but it could<br>
> > > also cause something in Gtk/Hildon (at least I have checked<br>
> > all places<br>
> > > deleting windows in hildon-desktop to no avail).<br>
> ><br>
> ><br>
> > Finally I found the reason for hiding the menu! It's in<br>
> > libhildon<br>
> > function hildon_app_menu_find_intruder. It thinks that the<br>
> > window with<br>
> > the "This is an RGBA window" label is an "intruder" (such as<br>
> > dialog<br>
> > etc.) and closes the menu as soon as it is mapped. This seems<br>
> > like a<br>
> > bug since the menu should not be mapped in the first place if<br>
> > this<br>
> > "intruder" is already there at mapping time.<br>
> ><br>
> > To summarize: this is libhildon bug and hildon-desktop is<br>
> > completely<br>
> > innocent (at last...)! ;)<br>
> ><br>
> > -Kimmo<br>
> ><br>
> ><br>
> > ><br>
> > > -Kimmo<br>
> > ><br>
> > > > --<br>
> > > > Luca Donaggio<br>
> > > ><br>
> > > > 2009/11/10 Kimmo Hämäläinen <<a href="mailto:kimmo.hamalainen@nokia.com">kimmo.hamalainen@nokia.com</a>><br>
> > > > On Tue, 2009-11-10 at 14:12 +0100, ext Luca<br>
> > Donaggio wrote:<br>
> > > > > Hi Kimmo,<br>
> > > > ><br>
> > > > > I'm sorry to bother you again, but the problem<br>
> > I'm facing is<br>
> > > > not how<br>
> > > > > to get a transparent window, but that if I<br>
> > create such a<br>
> > > > window the<br>
> > > > > HildonAppMenu of its parent HildonWindow doesn't<br>
> > show<br>
> > > > anymore.<br>
> > > > > I (slightly) modified your code to exemplify my<br>
> > situation.<br>
> > > ><br>
> > > ><br>
> > > > Ah, yes, I can see it. Looks like the menu is<br>
> > unmapped<br>
> > > > immediately when<br>
> > > > it is shown. It's weird, I'm not yet sure what<br>
> > unmaps it...<br>
> > > > Now it<br>
> > > > looks like hildon-desktop is not unmapping it, so<br>
> > it could be<br>
> > > > widget<br>
> > > > side problem also. I'll try to find out.<br>
> > > ><br>
> > > > BTW. this problem is not related to the<br>
> > transparency: opaque<br>
> > > > window does<br>
> > > > the same.<br>
> > > ><br>
> > > > -Kimmo<br>
> > > ><br>
> > > ><br>
> > > > ><br>
> > > > ><br>
> > > > > Thanks for your time,<br>
> > > > ><br>
> > > > > Luca Donaggio<br>
> > > > ><br>
> > > > > 2009/11/10 Kimmo Hämäläinen<br>
> > <<a href="mailto:kimmo.hamalainen@nokia.com">kimmo.hamalainen@nokia.com</a>><br>
> > > > > Hi,<br>
> > > > ><br>
> > > > > Sorry, took some time, I was busy with<br>
> > some bug<br>
> > > > fixing... I<br>
> > > > > started<br>
> > > > > with the Home applet example and managed<br>
> > to whip up<br>
> > > > a small<br>
> > > > > example<br>
> > > > > (attached) that shows a transparent pop-<br>
> > up window.<br>
> > > > ><br>
> > > > > -Kimmo<br>
> > > > ><br>
> > > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > ><br>
> ><br>
> > > _______________________________________________<br>
> > > maemo-developers mailing list<br>
> > > <a href="mailto:maemo-developers@maemo.org">maemo-developers@maemo.org</a><br>
> > > <a href="https://lists.maemo.org/mailman/listinfo/maemo-developers" target="_blank">https://lists.maemo.org/mailman/listinfo/maemo-developers</a><br>
> ><br>
> ><br>
> ><br>
><br>
> _______________________________________________<br>
> maemo-developers mailing list<br>
> <a href="mailto:maemo-developers@maemo.org">maemo-developers@maemo.org</a><br>
> <a href="https://lists.maemo.org/mailman/listinfo/maemo-developers" target="_blank">https://lists.maemo.org/mailman/listinfo/maemo-developers</a><br>
<br>
</div></div></blockquote></div><br>