freenode/#clim - IRC Chatlog
Search
14:55:41
jackdaniel
dim: see this: https://common-lisp.net/project/mcclim/static/documents/mcclim.pdf#Using%20incremental%20redisplay
15:53:58
slyrus1
there's some difficult-but-not-impossible-to-reproduce bug with dragging where one stops dragging but McCLIM doesn't realize it and then you can't ever stop dragging until you kill the process.
16:08:41
slyrus1
of course I really want flicker-free dragging feedback too so maybe I should worry about that first
16:10:59
TMA
the usual method to miss the 'dragging stops now' event is to release the held mouse button while another application is under cursor/after an app switch by some keyboard shortcut/when a pop-up from another application gains focus
16:12:39
TMA
however to stop dragging, it is usually sufficient just to click inside the apllication as the clicking resets the dragging status
16:43:08
jackdaniel
Colleen: tell scymtym that I've found one particular thing annoying when using clim.flamegraph (hard to say - McCLIM or appliaction fault): when I click the intervals interactor tries to print these large sample arrays what halts the application
16:43:08
Colleen
scymtym: Unknown command. Possible matches: 8, time, tell, set, say, mop, get, time in, have a, grant,
16:43:17
jackdaniel
Colleen tell scymtym: that I've found one particular thing annoying when using clim.flamegraph (hard to say - McCLIM or appliaction fault): when I click the intervals interactor tries to print these large sample arrays what halts the application
16:43:44
jackdaniel
Colleen tell scymtym: that's why I've removed locally interactor from the frame whatsoever
16:45:52
jackdaniel
::notify scymtym I've found one particular thing annoying when using clim.flamegraph (hard to say - McCLIM or appliaction fault): when I click the intervals interactor tries to print these large sample arrays what halts the application, that's why I've removed locally interactor from the frame whatsoever.
16:46:18
jackdaniel
I find minion's syntax much more pleasent to interact with (I never remember how to "use" Colleen)
16:48:09
dim
using incremental-display and then updating-output then the content is not redrawn in several cases
16:49:47
jackdaniel
these parts of code are not well tested (so if you can split these cases into simple orthoghonal instructions to reproduce and report issues, that will be a welcomed contribution - also it will increase a likehood of fixing them)
16:50:21
scymtym
jackdaniel: yeah, that's a problem. i wonder whether selecting individual samples even makes sense
16:50:21
Colleen
scymtym: jackdaniel said 4 minutes, 29 seconds ago: I've found one particular thing annoying when using clim.flamegraph (hard to say - McCLIM or appliaction fault): when I click the intervals interactor tries to print these large sample arrays what halts the application, that's why I've removed locally interactor from the frame whatsoever.
16:51:00
jackdaniel
dim: it may be one issue with multiple code snippets showing different issue manifestations, or one code snippet with clearly commented failure modes (and how to reproduce)
17:06:38
dim
jackdaniel: from commands, when I use commands (from the menu or otherwise), nothing gets redisplayed, but I have commands that change the cells
17:07:41
jackdaniel
I *think* that with incremental-redisplay you need to tell which cells need to be updated
17:11:07
dim
jackdaniel: is that the same thing? http://bauhh.dyndns.org:8000/clim-spec/21-1.html#_1017 the anchor in the PDF didn't work with safari
17:12:40
dim
currently redisplaying works fine in the game, mostly, with some bugs sometimes, but doesn't work when I run commands
17:12:52
jackdaniel
I don't have much experience with incremental-redisplay, I'm only aware it exists and may be used to speed up things (because you redisplay only damaged parts)
17:14:02
dim
ok I'm back to not using it at the moment, I think my understanding of it is too poor at the moment
17:23:49
dim
maybe I should write an Othello again, with the IA and all, like I did back ~20 years ago at school… though it was in Java, then Java+C (client/server), then one member of the team redid it in Javascript/C, then full javascript
17:24:07
slyrus1
yay. editable ellipses. needs incremental redisplay and maybe some faster ellipse math.
17:27:47
scymtym
jackdaniel: i didn't read closely enough what you wrote. were you trying to adjust the interval bounds or did you intentionally click one of the points?
18:06:57
jackdaniel
scymtym: it is hard to tell, because I have this X11 bug with patterns starting at screen's 0,0 (instead of window's [0,0]), basically window looks like this here: http://i.imgur.com/XH6OR9Z.png
18:07:15
jackdaniel
I click black area and sometimes it's fine and sometimes it prints on the interactor pane
18:22:50
scymtym
jackdaniel: i see. it really looks different (in part because you are using an older version). it is probably best to wait until the xrender work is merged
18:39:46
slyrus1
jackdaniel: sometimes I get funky ellipse drawing e.g. https://github.com/slyrus/clim-paint/issues/1
18:49:29
jackdaniel
slyrus1: rotated ellipses are drawn in quite peculiar way (due to lack of primitives in clx): we scan them horizontally (line by line) and draw intersecting lines; then we scan them vertically (to improve drawing quality)
18:50:45
jackdaniel
we should approximate drawing them with bezier curves (8 bezier curves for whole ellipse gives a very appealing result according to the article I've read)
20:13:46
slyrus1
I think we should rename the bezier segment point accessors. p0, p1, p2, p3 was a bad idea.
21:01:17
jackdaniel
afair there is no definite set of points (there may be 100 points), so more consistent approach (with other regions) would be having them in a sequence
22:19:33
slyrus1
p0 p1 p2 p3 are the points of a single bezier segment. No need for those symbols to be exported, IMO.
1:14:39
slyrus1
Does anyone understand the comment about "Defunct and not really nice..." regarding the presentation-to-command-translator in town-example.lisp?
1:14:57
slyrus1
That's the sort of thing we should clean up/remove lest we scare off future CLIM programmers.