Re: Preventing a window going to front - moving a window
- From: lecas malecas <darkiiiiii gmail com>
- To: Chris Vine <chris cvine freeserve co uk>
- Cc: gtkmm-list gnome org
- Subject: Re: Preventing a window going to front - moving a window
- Date: Tue, 6 Sep 2011 19:02:18 +0100
I did a bit more testing, the move() function works well, I tried
calling it with some numbers.
The problem is really with the get_position(), which returns always 0
(for x and y).
I think I'm calling it right (the compiler doesn't complain at least :p).
I have this on the function that gets called on the signal_hide():
this->get_position (x_position, y_position);
cout << "ONHIDE x " << x_position << " y " << y_position << endl;
where x_position and y_position are integers of the class.
On Mon, Sep 5, 2011 at 9:54 PM, lecas malecas <darkiiiiii gmail com> wrote:
> The realize event didn't worked, but the idle did. thanks!
>
> And the get_position(), any ideas on that?
>
> On Mon, Sep 5, 2011 at 9:37 PM, Chris Vine <chris cvine freeserve co uk> wrote:
>> On Mon, 05 Sep 2011 20:05:34 +0200
>> Yann LEYDIER <yann leydier info> wrote:
>>> last time I had to do something at init and it didn't fit in the
>>> constructor, I connected a method to the realize event.
>>
>> Or if the realize event doesn't do what is wanted (it may be stacked in
>> the glib event loop with other GDK drawing callbacks too early to
>> set the Z-order), the best approach would probably be to connect an
>> idle handler. That will be stacked in the main loop event list after
>> any GDK drawing functions have been called, assuming default idle
>> priority is chosen.
>>
>> Chris
>> _______________________________________________
>> gtkmm-list mailing list
>> gtkmm-list gnome org
>> http://mail.gnome.org/mailman/listinfo/gtkmm-list
>>
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]