freenode/#clim - IRC Chatlog
Search
13:24:20
slyrus1
jackdaniel: let me know if you have a minute to hear about my problems accepting values.
14:17:11
slyrus1
jackdaniel: first problem described here: https://github.com/slyrus/clim-presentation-test/issues/1
14:17:38
slyrus1
So I've made a simple app an am trying to figure out how to work with presentations and accepting values.
14:18:08
slyrus1
but I keep running into problems. Initially I thought it was things I doing wrong, now I'm thinking that I have both a McCLIM bug and an SBCL bug.
14:18:21
slyrus1
the first issue descrbies the McCLIM problem. The second will describe the SBCL problem.
14:20:55
slyrus1
it's entirely possible I'm doing something bogus in my application, but I can't find out what, if anything, I'm doing wrong.
14:27:23
slyrus1
and now I can't trigger the SBCL bug. grumble... hmm... One of the reasons I'm interested in the seeming SBCL problem is that that same failure mode (type mismatch in the guts of CLX) shows up in other contexts (like when I have non-trivial transformations on a sheet.
14:28:48
jackdaniel
OK, so as of first McCLIM bug: specialization on region region takes precedense over specialization on t drei:drei-area
14:30:38
jackdaniel
I'm not clos expert, so I don't know what would be a clean solution in this scenario
14:32:08
jackdaniel
sure, when you specialize on both areas you may get somewhere, but you'll still have an abstraction leak
14:32:30
jackdaniel
(region-union my-standard-rectangle my-drei-area) will use general sepcialization *again*
14:33:16
slyrus1
It strikes me that maybe calling region-union on the drei-area it self is bogus and maybe it should be fixed at the call site.
14:34:48
jackdaniel
as I said, *working* solution would be adding specialization on region for unspecialized arguments
14:50:15
slyrus1
jackdaniel: Ok, so just change the method signatures to: ((region1 drei-area) (region2 region)) and vice versa? That seems to fix the problem.
15:37:10
slyrus1
should these be explicit calls to e.g. region-union or should we use call-next-method?