freenode/#clim - IRC Chatlog
Search
22:26:10
jackdaniel
a) bounding rectangles are immutable; b) output recoreds implement a bounding rectangle protocol; c) a and b are inconsistent
22:26:48
jackdaniel
by inconsistent I mean that specification tells, that bounding rectangle of the output record may change under certain circumstances (but it can't) etc
5:19:34
loke
jackdaniel: But I had a problem creating a custom output record. Inheriting from OUTPUT-RECORD requires me to implement a whole lot of methods, and then I sumbled on a roadblock that is kinda weird
5:25:57
loke
I get an error saying that a method is undefined. It seems to be leaking some internal implementation (related to DEFMETHOD*, I think):
5:25:59
loke
#<STANDARD-GENERIC-FUNCTION (COMMON-LISP:SETF CLIM::.OUTPUT-RECORD-POSITION-STAR.) (14)>
6:05:10
loke
In this case, the cause is because my popup-completions box accepts a list of output records to display in the menu.
6:05:59
loke
That made me think: Perhaps it would make sense to have an easier way to create an output record that has the dimensions of the "old style", instead of happing the app developer implement their own.
7:04:15
jackdaniel
that sounds like a maintainance nightmare if you ask me. I don't have a strong opinion what shoul be returned as a bounding rectangle of the output record, but having it both ways is not a sound idea