00:26.17 | allejo | you know me so well :') |
00:27.07 | allejo | what's the diff between threadstart and thread? |
00:44.03 | macsforme | @@ -1 +1 @@ |
00:44.03 | macsforme | -threadstart |
00:44.03 | macsforme | +thread |
00:48.06 | allejo | lol |
01:01.58 | blast007 | ~macsforme++ |
01:17.12 | JeffM | The thread is he thread, threadstart is the arguments to the Thread when it starts, like priority and entry point |
01:20.24 | *** join/#bzflag infobot (ibot@rikers.org) |
01:20.24 | *** topic/#bzflag is https://BZFlag.org || http://ohloh.net/p/bzflag || https://bzflag.org/help || Channel Logs: http://infobot.rikers.org/%23bzflag/ || 2.4.12 released! https://forums.bzflag.org/viewtopic.php?f=62&t=19720 |
01:20.25 | *** mode/#bzflag [+v infobot] by ChanServ |
01:32.02 | JeffM | Blast in that mode itâs doing composition for the windows system and canât let a single app override the entire go context, since itâs used for all displays . |
01:37.34 | blast007 | some thread made it sound like it had something to do with display scaling vs GPU scaling |
01:40.31 | JeffM | It may be intended for multiple physical displays |
02:18.52 | the_map | lol macsforme |
02:37.52 | *** join/#bzflag Dracos85 (~dracos85@24-119-188-253.cpe.cableone.net) |
07:39.42 | JeffM | blast007: saw the page you did, thatâs the diff between 2 pipeline modes not on vs off. It has to do with forcing a non compositing window system to composite anyway. Itâs reported to have issues and be slow. My guess is it disables individual context gamma for a global gamma. Mostly itâs to help with tearing, forcing the render pipeline to draw all contexts at the same time for the same frame. |
07:47.02 | *** join/#bzflag john__ (~john@c-73-109-83-120.hsd1.wa.comcast.net) |
07:47.25 | *** join/#bzflag Guest51157 (~john@c-73-109-83-120.hsd1.wa.comcast.net) |
10:29.52 | *** join/#bzflag BZnotify (BZnotify@gateway/service/github.com/x-vcmixkqjeggeubbg) |
10:29.52 | BZnotify | [13bzflag] 15yason opened pull request #95: C++ Defect Report Core Issue 1344. (062.4...062.4) 02https://git.io/vboQY |
10:29.52 | *** part/#bzflag BZnotify (BZnotify@gateway/service/github.com/x-vcmixkqjeggeubbg) |
11:46.20 | *** join/#bzflag therealtbe (626fddbc@gateway/web/cgi-irc/kiwiirc.com/ip.98.111.221.188) |
12:25.21 | blast007 | JeffM: ah |
18:07.58 | *** join/#bzflag nadir (uid134094@gateway/web/irccloud.com/x-dolgitiduffoikhy) |
22:49.03 | *** join/#bzflag bertman (~bert@unaffiliated/bertman) |
23:25.07 | JeffM | do flag IDs have to be contiguous? |
23:56.28 | blast007 | JeffM: are you meaning in terms of a normal BZFlag client remaining compatible with another implementation of bzfs? |
23:57.41 | JeffM | yes |
23:58.04 | JeffM | are flags ever "destroyed"? or just maked as non-existant? |
23:58.34 | JeffM | because there is the FlagNoExist state |