2023-09-25 00:00:05 +0200 | vanvik | (~vanvik@78.156.11.181) (Ping timeout: 240 seconds) |
2023-09-25 00:00:18 +0200 | vanvik | (~vanvik@78.156.11.181) |
2023-09-25 00:05:21 +0200 | scardinal | (~supreme@87.61.100.169) (Ping timeout: 244 seconds) |
2023-09-25 00:12:05 +0200 | scardinal | (~supreme@87.61.100.169) |
2023-09-25 01:22:31 +0200 | chomwitt | (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1) (Ping timeout: 264 seconds) |
2023-09-25 02:22:25 +0200 | <haskellbridge> | <Ren> I was hoping someone could help me understand XMonad's behavior. I've been playing around with making my own GTK app to have as a desktop background so it has the window hint GDK_WINDOW_TYPE_HINT_DESKTOP, and the docks XConfig correctly ignores it letting it sit in the background, but by doing so it puts a complete stop to mouse-over switching screens. Without my desktop backgrou |
2023-09-25 02:22:25 +0200 | <haskellbridge> | <clipped message> |
2023-09-25 02:22:26 +0200 | <haskellbridge> | <Ren> nd app running, the screen focus switches as I move my mouse between monitors even if those screen are devoid of any windows to actually focus on. How can I maintain this feature while still having a desktop app? Is it even possible? |
2023-09-25 02:23:27 +0200 | <geekosaur> | no. X11 limitation |
2023-09-25 02:23:56 +0200 | <geekosaur> | well, might work if your program ignores Xinerama/XRandR and covers the entire root window |
2023-09-25 02:24:27 +0200 | <geekosaur> | but I suspect not because the root window is treated specially by XRandR |
2023-09-25 02:26:09 +0200 | <haskellbridge> | <Ren> That's too bad, and I've gotten so used to the convenience too. This is my first time using GTK and trying to dive into this stuff in general, so I wouldn't know how to try out that root window thing, but I'll keep it in mind as I learn |
2023-09-25 02:26:41 +0200 | <haskellbridge> | <Ren> Thanks for the quick answer |
2023-09-25 02:26:55 +0200 | <geekosaur> | an alternative might be to draw directly into the root window instead of creating your own desktop window |
2023-09-25 03:00:32 +0200 | <haskellbridge> | <Ren> I certainly don't know how to do that at the moment, would that even maintain the interactivity of the program? |
2023-09-25 03:20:33 +0200 | <geekosaur> | no |
2023-09-25 03:37:06 +0200 | <haskellbridge> | <Ren> Yeah, I just experimented some with xwinwrap, I'll wager a guess that the X11 limitation involves the window capturing input since not passing -ni (no input) to xwinwrap also puts an end to automatic screen switching |
2023-09-25 03:38:18 +0200 | <geekosaur> | it's a little more complex than that |
2023-09-25 03:38:44 +0200 | <geekosaur> | multiple screens in X11 are a big hack involving the root window, so only the root window is actually aware of multiple screens |
2023-09-25 03:43:10 +0200 | <haskellbridge> | <Ren> So, mousing over the root window, and information on what screen it is can be gathered, but any other window has no idea what screen it is on? |
2023-09-25 03:48:08 +0200 | <geekosaur> | essentially, yes |
2023-09-25 03:48:14 +0200 | <geekosaur> | that's a large part of the hack |
2023-09-25 03:49:18 +0200 | <geekosaur> | all the monitors are carved out of the root window; normal windows generally stick to a monitor. and mouse position is reported relative to the window's upper left corner, so only the root which spans all monitors knows the mouse's true position |
2023-09-25 03:49:54 +0200 | <geekosaur> | which is why I suggested trying to create a window spanning the entire root; hopefully it'll work the same way. but gtk will fight it |
2023-09-25 03:58:30 +0200 | <haskellbridge> | <Ren> Well just going with what I know, making the window span both my screens results is functionally the same result as just having it on my first monitor, so I think the screen it knows about is the one where it's origin in, even though it spans both monitors. I suppose if one could send a message to XMonad and ask to switch to n screen, It could be possible to recreate the original |
2023-09-25 03:58:30 +0200 | <haskellbridge> | <clipped message> |
2023-09-25 03:58:31 +0200 | <haskellbridge> | <Ren> behavior, since the gdk library has enough info to build a full model of my screens |
2023-09-25 03:59:46 +0200 | <haskellbridge> | <Ren> But that is also probably not so simple, if at all possible since I doubt it is getting mouse events a lot since most of the time, windows are on top of it |
2023-09-25 04:12:21 +0200 | td_ | (~td@i5387092C.versanet.de) (Ping timeout: 258 seconds) |
2023-09-25 04:13:59 +0200 | td_ | (~td@i53870932.versanet.de) |
2023-09-25 07:34:03 +0200 | chomwitt | (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1) |
2023-09-25 09:11:07 +0200 | chomwitt | (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1) (Ping timeout: 264 seconds) |
2023-09-25 09:17:25 +0200 | chomwitt | (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1) |
2023-09-25 09:43:33 +0200 | hightower2 | (~hightower@141-136-211-208.dsl.iskon.hr) (Ping timeout: 258 seconds) |
2023-09-25 10:10:37 +0200 | matijja | (~matijja@193.77.181.201) (Quit: ZNC 1.8.2 - https://znc.in) |
2023-09-25 10:11:29 +0200 | matijja | (~matijja@193.77.181.201) |
2023-09-25 10:18:13 +0200 | hightower2 | (~hightower@85.94.71.188) |
2023-09-25 10:24:50 +0200 | cfricke | (~cfricke@user/cfricke) |
2023-09-25 10:56:35 +0200 | cfricke | (~cfricke@user/cfricke) (Ping timeout: 240 seconds) |
2023-09-25 11:02:05 +0200 | cfricke | (~cfricke@user/cfricke) |
2023-09-25 11:21:48 +0200 | chomwitt | (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1) (Ping timeout: 240 seconds) |
2023-09-25 12:09:30 +0200 | ft | (~ft@p3e9bc680.dip0.t-ipconnect.de) (Quit: leaving) |
2023-09-25 12:56:13 +0200 | srk- | (~sorki@user/srk) |
2023-09-25 12:58:47 +0200 | srk| | (~sorki@user/srk) |
2023-09-25 12:59:19 +0200 | srk | (~sorki@user/srk) (Ping timeout: 244 seconds) |
2023-09-25 13:01:55 +0200 | srk| | srk |
2023-09-25 13:02:29 +0200 | srk- | (~sorki@user/srk) (Ping timeout: 255 seconds) |
2023-09-25 13:23:15 +0200 | raghavgururajan_ | (ea769b8000@2604:bf00:561:2000::242) |
2023-09-25 13:23:20 +0200 | zoglesby_ | (f0f8ca1525@2604:bf00:561:2000::64) |
2023-09-25 13:24:00 +0200 | samhh__ | (7569f027cf@2604:bf00:561:2000::e4) |
2023-09-25 13:25:57 +0200 | chomwitt | (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1) |
2023-09-25 13:27:55 +0200 | alethkit_ | (23bd17ddc6@sourcehut/user/alethkit) |
2023-09-25 13:30:55 +0200 | jludwig | (~justin@li657-110.members.linode.com) (*.net *.split) |
2023-09-25 13:30:56 +0200 | alethkit | (23bd17ddc6@sourcehut/user/alethkit) (*.net *.split) |
2023-09-25 13:30:57 +0200 | samhh | (7569f027cf@2604:bf00:561:2000::e4) (*.net *.split) |
2023-09-25 13:30:58 +0200 | zoglesby | (f0f8ca1525@user/zoglesby) (*.net *.split) |
2023-09-25 13:30:58 +0200 | raghavgururajan | (ea769b8000@user/raghavgururajan) (*.net *.split) |
2023-09-25 13:30:58 +0200 | B-J | (~BenziJuni@88-149-64-112.du.xdsl.is) (*.net *.split) |
2023-09-25 13:31:03 +0200 | alethkit_ | alethkit |
2023-09-25 13:31:06 +0200 | zoglesby_ | zoglesby |
2023-09-25 13:31:19 +0200 | alethkit | (23bd17ddc6@sourcehut/user/alethkit) (Read error: Connection reset by peer) |
2023-09-25 13:31:19 +0200 | samhh__ | (7569f027cf@2604:bf00:561:2000::e4) (Write error: Connection reset by peer) |
2023-09-25 13:31:19 +0200 | zoglesby | (f0f8ca1525@2604:bf00:561:2000::64) (Write error: Connection reset by peer) |
2023-09-25 13:31:21 +0200 | raghavgururajan_ | (ea769b8000@2604:bf00:561:2000::242) (Write error: Connection reset by peer) |
2023-09-25 13:31:29 +0200 | zoglesby | (f0f8ca1525@2604:bf00:561:2000::64) |
2023-09-25 13:31:30 +0200 | raghavgururajan | (ea769b8000@2604:bf00:561:2000::242) |
2023-09-25 13:31:39 +0200 | raghavgururajan | (ea769b8000@2604:bf00:561:2000::242) (Changing host) |
2023-09-25 13:31:39 +0200 | raghavgururajan | (ea769b8000@user/raghavgururajan) |
2023-09-25 13:31:41 +0200 | zoglesby | (f0f8ca1525@2604:bf00:561:2000::64) (Changing host) |
2023-09-25 13:31:41 +0200 | zoglesby | (f0f8ca1525@user/zoglesby) |
2023-09-25 13:32:56 +0200 | samhh_ | (7569f027cf@2604:bf00:561:2000::e4) |
2023-09-25 13:33:27 +0200 | alethkit | (23bd17ddc6@sourcehut/user/alethkit) |
2023-09-25 13:35:05 +0200 | jludwig | (~justin@li657-110.members.linode.com) |
2023-09-25 13:35:05 +0200 | B-J | (~BenziJuni@88-149-64-112.du.xdsl.is) |
2023-09-25 14:13:51 +0200 | cfricke | (~cfricke@user/cfricke) (Quit: WeeChat 4.0.4) |
2023-09-25 15:15:07 +0200 | chomwitt | (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1) (Remote host closed the connection) |
2023-09-25 15:15:31 +0200 | chomwitt | (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1) |
2023-09-25 15:20:30 +0200 | pantsu | (~Urist@archlinux/op/MrElendig) (Quit: all hail donk) |
2023-09-25 15:21:38 +0200 | MrElendig | (~Urist@archlinux/op/MrElendig) |
2023-09-25 15:41:13 +0200 | chomwitt | (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1) (Ping timeout: 240 seconds) |
2023-09-25 16:29:22 +0200 | hightower2 | (~hightower@85.94.71.188) (Ping timeout: 260 seconds) |
2023-09-25 16:36:02 +0200 | chomwitt | (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1) |
2023-09-25 16:53:00 +0200 | chomwitt | (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1) (Ping timeout: 240 seconds) |
2023-09-25 17:01:49 +0200 | hightower2 | (~hightower@141-136-211-208.dsl.iskon.hr) |
2023-09-25 17:27:52 +0200 | chomwitt | (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1) |
2023-09-25 18:20:04 +0200 | chomwitt | (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1) (Remote host closed the connection) |
2023-09-25 22:52:58 +0200 | ft | (~ft@p3e9bc680.dip0.t-ipconnect.de) |
2023-09-25 23:08:21 +0200 | exordiri | (~ex@user/exordiri) (Remote host closed the connection) |