[mcclim-cvs] CVS update: mcclim/Backends/beagle/README.txt
Duncan Rose
drose at common-lisp.net
Fri Jun 3 21:33:10 UTC 2005
Update of /project/mcclim/cvsroot/mcclim/Backends/beagle
In directory common-lisp.net:/tmp/cvs-serv26518/beagle
Modified Files:
README.txt
Log Message:
Implement 'pseudo' pointer grabbing. Get rid of redefinition of pointer
tracking loop from frame-manager.lisp (can use usual definition now
PORT-GRAB-POINTER etc. are implemented).
Date: Fri Jun 3 23:33:08 2005
Author: drose
Index: mcclim/Backends/beagle/README.txt
diff -u mcclim/Backends/beagle/README.txt:1.13 mcclim/Backends/beagle/README.txt:1.14
--- mcclim/Backends/beagle/README.txt:1.13 Fri Jun 3 00:17:27 2005
+++ mcclim/Backends/beagle/README.txt Fri Jun 3 23:33:08 2005
@@ -146,6 +146,8 @@
to do with McCLIM not understanding where the pointer is, or something to
do with tracking-pointer.
+ (Doesn't appear to be anything to do with tracking pointer...)
+
!21. Highlighting on mouse overs isn't quite right; artefacts are left on the
display after the mouse has moved out of the target object bounding
@@ -274,6 +276,14 @@
long-lived operation (generating a big graph, for example), some of
those events are 'trapped' in the queue until other events take place.
Looking at the code, I don't think this should happen... (but it does).
+
+
+30. Event handling over 'drop down' menus is strange; after clicking on the
+ menu name, all events appear to be blocked until the mouse button is
+ released (no drag events or anything). After release, the events are
+ processed (but then it's too late, the menu is gone). Note that this is
+ *nothing* to do with tracking pointer, which appears not to be used in
+ drop down menus (only popup menus, which work, more or less).
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
More information about the Mcclim-cvs
mailing list