>1) I found the same instability that I had on the duo

Will test specifically for that...

>2) Double-clicking in the Finder is improved somewhat, but still quite
>   unreliable (except on my duo, of course...)
>   I very strongly suspect this is *not* a CursorDevice debouncing
>   problem, as was originally suggested (after all, double-clicks seem
>   to work elsewhere), but is actually because of the way that the
>   Finder 'locks up' the machine for a fraction of a second after a
>   click on an icon (after some testing I realised the length of time
>   is dependent on the 'double-click' time set in the Mouse control
>   panel - this suggests that the Finder is taking over monitoring of
>   the mouse after a mouse-down so that it can check for various
>   things like contextual menus etc - it might be worth trying with
>   this switched off to see if the problem persists).

Interesting - I find it fairly unreliable too, but it worked "well enough"
from WinVNC.  I'll try fiddling with some code, and see if I can get it to
give extra time back to the system in between mouse button transitions,
which should help if the Finder really is doing it's own double-click
handling.

>3) With the removal of the interrupt code that allowed receiving of
>   information at interrupt time, there are a few minor oddities with
>   regard to cursor tracking on slower Macs (for example, with the
>   'drag-selection' of icons - the 'elastic-band' sometimes does not
>   appear when it should).

Again, interesting - though might be coupled more to System version than
CPU speed, since I can only use 9.0.4 on my spanking new PowerBook.
Probably worth my testing on System 7.5.5.

>1) Apart from the above problem (which only seems to happen when the
>   server app is frontmost) the alpha 3 release does appear to be very
>   robust.
>
>2) The encoding bugs have been dealt with (the background problem and
>   the occasional rect errors, as well as CoRRE now being correctly
>   activated).
>
>3) The hardware cursor looks like it is working well.

Good, although it will only display the B&W version of a cursor (I can't
figure out how to get an unpacked version of the colour one) which
shouldn't be a massive problem for most users.

>Of course, the drag problem remains (are you getting anywhere with
>that, Jonathan?) with the standard vncPatches.

I won't get anywhere with it until I can figure out how to call a
UniversalProcPtr from 68k assembler. Maybe you could help with that...

>With regard to an alpha 3 version of vncPatches68k, I have completed
>a version, but I'm finding a rather odd case where it occasionally
>misses some updates - you have to wipe across with the cursor to see
>it. I don't know why this should be (yet) since the coding for the
>update capturing (and buffering etc) has not changed since alpha 1.

Maybe your (or my) re-entrancy code needs updating so that it cannot
attempt to send updates to the server during sending of an update.  That's
the only situation I can think of in my code where corruption of the update
region could occur.

>There's also some anomalous problems I've been having with the
>modifier keys (the shift key in particular - rather odd, again, but
>I suspect it has to do with the way that the server app and the
>patches are interacting together on the low level keymapping stuff).

I put in the overwriting-low-memory patch you suggested, so it is no longer
needed in your patches.  Has this been taken into account?

--------------------------------------------------------------
from:     Jonathan "Chromatix" Morton
mail:     [EMAIL PROTECTED]  (not for attachments)
big-mail: [EMAIL PROTECTED]
uni-mail: [EMAIL PROTECTED]

The key to knowledge is not to rely on people to teach you it.

Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/

-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a19 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r- y+
-----END GEEK CODE BLOCK-----
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------

Reply via email to