![vnc server for mac vnc server for mac](https://cdn4.geckoandfly.com/wp-content/uploads/2016/09/tigervnc.jpg)
Vnc server for mac driver#
You write the reference ID of your driver to journalRef, and you set journalFlag to whether you want it to record or playback. So the idea with the journaling driver is pretty simple. sometimes four seconds, maybe five if I got lucky. So I whipped up a desk accessory and lo and behold, it worked. Surely therein lay the solution to my problem. So while I was pulling my hair out over the MBState issue, I came across those two pages in the ancient scriptures (Inside Macintosh) about the Journaling driver and the fabled desk accessory Apple engineers had used to stress test the Mac UI.
Vnc server for mac code#
In the end, the solution was easy but non-obvious and I only came across it by carefully examining the disassembled code for the VIA interrupt, but this was after I had tried all the other hard things that did not and since you guys seem to be enjoying my deeds of Mac derring-do, let me tell you about my ordeal with the Journaling driver, for therein lies a tale.
Vnc server for mac plus#
Writing a button state to that low-memory variable works on later Macs, and is in fact what ChromiVNC does, but it does not work on the Mac Plus - therein was the problem. Things like jGNEFilters and patching traps don't work either, because the dragging routines don't rely on events, they rely on low-memory button state global which on the Mac Plus is continually overwritten by the VIA interrupt. In the end, I concluded the journaling mechanism was borked when Apple introduced multitasking in System 7. It almost worked - just well enough to consume another month of my life chasing a false lead. But click and drag - that consumed three months of my life! Clicking is easy too - just post an event. Moving the mouse is relatively straightforward, it involves writing some low-memory global.
![vnc server for mac vnc server for mac](https://www.macupdate.com/images/icons512/61088.png)
It seems easy, doesn't it? I thought so too, but it actually took me three months to get the remote control to work. I also bet you could speed everything up on color Macs by skipping the offscreen B&W buffer blit and just doing the color-to-B&W conversion yourself pixel-by-pixel in a tight loop before streaming out the bitmap over TCP. The mouse is frozen by the CrsrState change. It takes long enough that we can get multiple smashed We also want to freeze the mouse while this goes on, since we don't want the mouse to We do this by setting it invisible, and decrementing the CrsrState. We will mark the cursor as Invisible so that QD will think that it doesn't We need it there in order to make it a real screen The problem is that CopyBits will ShieldCursor in order to make it not This is to make the cursor visible in the pict, once it Here's what the implementor had to say about this trick: The short version is you need to futz with a couple lomem globals so CopyBits thinks the cursor is already hidden.