DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined #qi-hardware
strawberyargon has joined #qi-hardware
pcercuei has joined #qi-hardware
rodgort has quit [*.net *.split]
rodgort has joined #qi-hardware
DocScrutinizer05 has quit [*.net *.split]
Nik05 has quit [*.net *.split]
DocScrutinizer51 has quit [*.net *.split]
Ornotermes has quit [*.net *.split]
Ornotermes has joined #qi-hardware
DocAvalanche has joined #qi-hardware
DocAvalanche is now known as DocScrutinizer51
DocScrutinizer05 has joined #qi-hardware
Nik05 has joined #qi-hardware
<whitequark>
wpwrak: what do you want to get in TextWidget::set_cursor_hand ?
<whitequark>
DocScrutinizer05: what you say is correct, I just meant having such a debugging facility be flaky is annoying.
<wpwrak>
whitequark: i was thinking of something like if (get()->dpy_tw) gdkwin->set_cursor(Gdk::Cursor::create(get().dpy_tw, type); else gdkwin->set_cursor(Gdk::Cursor::create(type));
<wpwrak>
where dpy_tw is NULL if we don't use an alternative display, and points to the alternative display if we do
<wpwrak>
but ... get() isn't available, so i can't get at the TWGtk and thus can't get at dpy_tw :(
<wpwrak>
meanwhile, in "main", TW.get() works just fine
<wpwrak>
maybe there'd be also a way to just the "my display", whatever the context (i.e., alt or same as GW), but i wouldn't know how to obtain that sort of information
<whitequark>
wpwrak: you don't need get() here ever
<whitequark>
or explicitly saving the display anyway
<whitequark>
you can call get_screen() or get_display() in any widget or window
<wpwrak>
hmm. let's see what happens ...
<whitequark>
also, you have never generally needed get().
<whitequark>
just use TW->dpy_tw if you have a field called dpy_tw
<whitequark>
again an XY problem...
<wpwrak>
naw. trying something more familiar before venturing into more treacherous territory
<wpwrak>
strange. TW->dpy_tw does indeed compile. but why ? dpy_tw is in TWGtk, not TW