From mcclim-devel at common-lisp.net Tue Mar 13 16:10:46 2007 From: mcclim-devel at common-lisp.net (mcclim) Date: Tue, 13 Mar 2007 16:10:46 -0000 Subject: [mcclim-ticket] #1: Bug in handling of delimiter/completion gestures in McCLIM input editing Message-ID: <078.ecce3bf677a1c792cc00bf84eb76201f@common-lisp.net> #1: Bug in handling of delimiter/completion gestures in McCLIM input editing ---------------------------------+------------------------------------------ Reporter: thenriksen | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: Drei, input-editing | ---------------------------------+------------------------------------------ Observe the following presentation type definition: {{{ (in-package :clim-user) (define-presentation-type unacceptable ()) (define-presentation-method accept ((type unacceptable) stream view &key) (with-delimiter-gestures (#\Space) (list (accept 'package :stream stream :view view :prompt nil) (accept 'package :stream stream :view view :prompt nil)))) }}} Using Drei, doing (accept 'unacceptable) will work while accepting the first package, but when you press space to accept the second one, a debugger will pop up and inform you that you did not provide any input, and that there is not a default value. I think the problem is that the delimiter gesture is "re-evaluated" as a terminating delimiter gesture. The problem does not show up with Goatee, because Goatee implements a non- standard hack with which you can inhabit rescanning by providing :rescan nil as argument to ''replace-input''. This is used in the completion done when pressing space after entering the first package name. I don't think the McCLIM input editing routines should expect input-editing-streams to implement nonstandard hacks in order to work properly, but I haven't yet been able to figure out how to fix this. In case anyone is interested, I think the buggy function is ''complete-input''. At least, that's where the ''replace-input''-call is. This is a very serious problem that prevents Drei from being able to accept many interesting presentation types, including some seen in classic CLIM applications. -- Ticket URL: mcclim mcclim From mcclim-devel at common-lisp.net Tue Mar 13 16:14:04 2007 From: mcclim-devel at common-lisp.net (mcclim) Date: Tue, 13 Mar 2007 16:14:04 -0000 Subject: [mcclim-ticket] Re: #1: Bug in handling of delimiter/completion gestures in McCLIM input editing In-Reply-To: <078.ecce3bf677a1c792cc00bf84eb76201f@common-lisp.net> References: <078.ecce3bf677a1c792cc00bf84eb76201f@common-lisp.net> Message-ID: <087.233651b0c92391265c22058bd0df3458@common-lisp.net> #1: Bug in handling of delimiter/completion gestures in McCLIM input editing -------------------------+-------------------------------------------------- Reporter: thenriksen | Owner: thenriksen Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Resolution: | Keywords: Drei, input-editing -------------------------+-------------------------------------------------- Changes (by thenriksen): * owner: somebody => thenriksen -- Ticket URL: mcclim mcclim From mcclim-devel at common-lisp.net Wed Mar 14 20:48:59 2007 From: mcclim-devel at common-lisp.net (mcclim) Date: Wed, 14 Mar 2007 20:48:59 -0000 Subject: [mcclim-ticket] #2: gtkairo: the slider needs tick marks Message-ID: <078.3b924395fb01c4e77e1d2743693d62e8@common-lisp.net> #2: gtkairo: the slider needs tick marks -------------------------+-------------------------------------------------- Reporter: dlichteblau | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | -------------------------+-------------------------------------------------- Gtkairo Bug 5b: The slider needs tick marks. -- Ticket URL: mcclim mcclim From mcclim-devel at common-lisp.net Wed Mar 14 20:59:46 2007 From: mcclim-devel at common-lisp.net (mcclim) Date: Wed, 14 Mar 2007 20:59:46 -0000 Subject: [mcclim-ticket] #3: gtkairo: incorrect default colors Message-ID: <078.241d720311de79de92cd72a54183f185@common-lisp.net> #3: gtkairo: incorrect default colors -------------------------+-------------------------------------------------- Reporter: dlichteblau | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | -------------------------+-------------------------------------------------- Gtkairo Bug 8: We are using frontend-specified colors (*3d-normal-color*) where the GTK+ theme should take precedence. Test case: Notice the two different shades of grey in the label-test. -- Ticket URL: mcclim mcclim From mcclim-devel at common-lisp.net Wed Mar 14 21:01:09 2007 From: mcclim-devel at common-lisp.net (mcclim) Date: Wed, 14 Mar 2007 21:01:09 -0000 Subject: [mcclim-ticket] #4: gtkairo: coordinate system confusion in the drag&drop example Message-ID: <078.fedc57c1d91bf16b36f85a895c7d3bd1@common-lisp.net> #4: gtkairo: coordinate system confusion in the drag&drop example -------------------------+-------------------------------------------------- Reporter: dlichteblau | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | -------------------------+-------------------------------------------------- Gtkairo Bug 10: Somewhere global mouse coordinates aren't turned into local coordinates correctly. (Watch the Drag&Drop test not work unless the window is in the upper left corner of the screen.) -- Ticket URL: mcclim mcclim From mcclim-devel at common-lisp.net Wed Mar 14 21:02:20 2007 From: mcclim-devel at common-lisp.net (mcclim) Date: Wed, 14 Mar 2007 21:02:20 -0000 Subject: [mcclim-ticket] #5: gtkairo: copy&paste ("selection") not implemented Message-ID: <078.0303def6069f5516c5989801a343a6d4@common-lisp.net> #5: gtkairo: copy&paste ("selection") not implemented -------------------------+-------------------------------------------------- Reporter: dlichteblau | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | -------------------------+-------------------------------------------------- Gtkairo Bug 21: Copy&paste needs to be implemented. -- Ticket URL: mcclim mcclim From mcclim-devel at common-lisp.net Wed Mar 14 21:09:52 2007 From: mcclim-devel at common-lisp.net (mcclim) Date: Wed, 14 Mar 2007 21:09:52 -0000 Subject: [mcclim-ticket] #6: gtkairo: cairo medium ellipse drawing and line styles Message-ID: <078.de3191f6df147145b807b407db291161@common-lisp.net> #6: gtkairo: cairo medium ellipse drawing and line styles -------------------------+-------------------------------------------------- Reporter: dlichteblau | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | -------------------------+-------------------------------------------------- Gtkairo Bug 22: The cairo version of medium-draw-ellipse* needs a rewrite. (The gdk medium can draw ellipses just fine, however.) The current implementation fills an ellipse, but completely fails when drawing its border: {{{ ;; This one is tricky. Cairo doesn't know ellipses, it only knows ;; circles. But then it is fully capable to draw circles under affine ;; transformations only that the line style is transformed too. So ;; what we do: We setup an [additional] transformation to from our ;; ellipse to a circle and setup line style properly transformed. --- ;; This is not entirely correct in case of shearing or odd scaling ;; transformations. }}} Unless cairo starts supporting ellipses natively, I would suggest using bezier curves to approximate an ellipse. -- Ticket URL: mcclim mcclim From mcclim-devel at common-lisp.net Wed Mar 14 21:10:37 2007 From: mcclim-devel at common-lisp.net (mcclim) Date: Wed, 14 Mar 2007 21:10:37 -0000 Subject: [mcclim-ticket] #7: gtkairo: layout troubles Message-ID: <078.03931424311b5ee9ade8dde081537212@common-lisp.net> #7: gtkairo: layout troubles -------------------------+-------------------------------------------------- Reporter: dlichteblau | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | -------------------------+-------------------------------------------------- Gtkairo Bug 23: Beirc problem: When connecting to a server, the first receiver pane is created, and suddenly the windows gets unusably large, hiding the interactor. Replacing the :min-height 800 in receivers.lisp with :min-height 400 :max-height 400 fixes that, but CLX doesn't have the same problem. -- Ticket URL: mcclim mcclim From mcclim-devel at common-lisp.net Wed Mar 14 21:16:47 2007 From: mcclim-devel at common-lisp.net (mcclim) Date: Wed, 14 Mar 2007 21:16:47 -0000 Subject: [mcclim-ticket] #8: gtkairo regression: method browser broken Message-ID: <078.9dfe193db9e943f990554ee9816ee7c0@common-lisp.net> #8: gtkairo regression: method browser broken -------------------------+-------------------------------------------------- Reporter: dlichteblau | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | -------------------------+-------------------------------------------------- The option panes in the method browser are not visible. This used to work just fine. -- Ticket URL: mcclim mcclim From mcclim-devel at common-lisp.net Wed Mar 14 21:19:27 2007 From: mcclim-devel at common-lisp.net (mcclim) Date: Wed, 14 Mar 2007 21:19:27 -0000 Subject: [mcclim-ticket] #9: gtkairo: slider flickering Message-ID: <078.619a3a542e48cd865c744d17ff721cd3@common-lisp.net> #9: gtkairo: slider flickering -------------------------+-------------------------------------------------- Reporter: dlichteblau | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | -------------------------+-------------------------------------------------- The native gtkairo slider flickers when it is being moved. (The only surprise here is that the scroll bars don't have that issue.) -- Ticket URL: mcclim mcclim From mcclim-devel at common-lisp.net Wed Mar 14 21:20:28 2007 From: mcclim-devel at common-lisp.net (mcclim) Date: Wed, 14 Mar 2007 21:20:28 -0000 Subject: [mcclim-ticket] #10: gtkairo class hierarchy misdesign Message-ID: <078.306ce2427b71f7c90a41d24dbcba720d@common-lisp.net> #10: gtkairo class hierarchy misdesign -------------------------+-------------------------------------------------- Reporter: dlichteblau | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | -------------------------+-------------------------------------------------- IIRC, Gtkairo subclasses generic gadget implementations instead of subclassing their abstract superclasses. -- Ticket URL: mcclim mcclim From mcclim-devel at common-lisp.net Wed Mar 14 21:23:27 2007 From: mcclim-devel at common-lisp.net (mcclim) Date: Wed, 14 Mar 2007 21:23:27 -0000 Subject: [mcclim-ticket] #11: gtkairo crash: tab layout and input focus Message-ID: <078.cbac35d98c0d2700ba5f4dfaf839bd5d@common-lisp.net> #11: gtkairo crash: tab layout and input focus -------------------------+-------------------------------------------------- Reporter: dlichteblau | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | -------------------------+-------------------------------------------------- To reproduce, just open the tab layout demo, then close it. (This used to work.) {{{ debugger invoked on a SIMPLE-ERROR in thread #: There is no applicable method for the generic function # when called with arguments (#). restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT] Return to application command loop 1: Exit debugger, returning to top level. ((SB-PCL::FAST-METHOD NO-APPLICABLE-METHOD (T)) # # # #) 0] }}} -- Ticket URL: mcclim mcclim From mcclim-devel at common-lisp.net Thu Mar 15 08:28:17 2007 From: mcclim-devel at common-lisp.net (mcclim) Date: Thu, 15 Mar 2007 08:28:17 -0000 Subject: [mcclim-ticket] Re: #2: gtkairo: the slider needs tick marks In-Reply-To: <078.3b924395fb01c4e77e1d2743693d62e8@common-lisp.net> References: <078.3b924395fb01c4e77e1d2743693d62e8@common-lisp.net> Message-ID: <087.e1b6aad34212b02d0694366d5884a663@common-lisp.net> #2: gtkairo: the slider needs tick marks --------------------------+------------------------------------------------- Reporter: dlichteblau | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: gtkairo | Version: Resolution: | Keywords: --------------------------+------------------------------------------------- Changes (by dlichteblau): * component: general => gtkairo -- Ticket URL: mcclim mcclim From mcclim-devel at common-lisp.net Tue Mar 27 17:46:11 2007 From: mcclim-devel at common-lisp.net (mcclim) Date: Tue, 27 Mar 2007 17:46:11 -0000 Subject: [mcclim-ticket] #12: Cosmetic differences between real GTK and mcclim with GTK backend that would be easy to fix Message-ID: <078.0ea839f2e613ba6b7319499e7bf3135b@common-lisp.net> #12: Cosmetic differences between real GTK and mcclim with GTK backend that would be easy to fix --------------------------+------------------------------------------------- Reporter: imikalajunas | Owner: dlichteblau Type: enhancement | Status: new Priority: minor | Milestone: Component: gtkairo | Version: Keywords: gtk | --------------------------+------------------------------------------------- Even with gtk scrollbars mcclim applications feel foreign, two small differences i have found are: Red outline - color of the pane is white in mcclim, and "default" or "button" in gtk. Blue outline - there is a border outside of the scroll pane in GTK so it's easier to discern which pane the scrollbar belongs to. [http://ignas.pov.lt/clim.png McClim screenshot] [http://ignas.pov.lt/xchat.png GTK screenshot] TRAC embeds pictures automatically, sorry. -- Ticket URL: mcclim mcclim From mcclim-devel at common-lisp.net Tue Mar 27 18:30:52 2007 From: mcclim-devel at common-lisp.net (mcclim) Date: Tue, 27 Mar 2007 18:30:52 -0000 Subject: [mcclim-ticket] Re: #12: Cosmetic differences between real GTK and mcclim with GTK backend that would be easy to fix In-Reply-To: <078.0ea839f2e613ba6b7319499e7bf3135b@common-lisp.net> References: <078.0ea839f2e613ba6b7319499e7bf3135b@common-lisp.net> Message-ID: <087.fbe868359ffbb68e6ef68dc7359d67ef@common-lisp.net> #12: Cosmetic differences between real GTK and mcclim with GTK backend that would be easy to fix ---------------------------+------------------------------------------------ Reporter: imikalajunas | Owner: dlichteblau Type: enhancement | Status: new Priority: minor | Milestone: Component: gtkairo | Version: Resolution: | Keywords: gtk ---------------------------+------------------------------------------------ Comment (by dlichteblau): Right, the visual differences are due to the fact that gtkairo's frame manager implements each SCROLL-BAR as GtkScrollbar, but doesn't implement the SCROLLER-PANE as a GtkScrolledWindow. As for "easy to fix", I have no idea how easy it would be to fix this. That the portable SCROLLER-PANE injects a VIEWPORT between itself and the actual child might turn out to be difficult to emulate without breaking applications. Advice from anyone who understands the scroller pane appreciated. -- Ticket URL: mcclim mcclim