Keeping track of your clipboard history
Issue: 10.6 (September/October 2012)
Author: Marc Zeedar
Article Description: No description available.
Article Length (in bytes): 10,356
Starting Page Number: 69
RBD Number: 10609
project10609.zip Updated: Tuesday, September 4, 2012 at 2:29 PM
Related Link(s): None
Known Limitations: None
Excerpt of article text...
Recently there was a post on the Tidbits mailing list (http://tidbits.com/pipermail/tidbits-talk/2012-August/009754.html) looking for a software program that would keep a log of all clipboard contents. This sounded intriguing to me, both because of its usefulness (as a writer, it might be handy to have a clipboard log) and because it sounded like a simple yet just challenging enough program to write in Real Studio.
By simple I meant that in concept the application seemed easy—just watch for any changes in the clipboard contents and then append the most recent clipboard to a file. But in practice it would be challenging—how do you monitor the clipboard status from within a Real Studio application?
My first thought was to write this as a faceless console application. It seemed logical to just have this running in the background saving copies of all clipboard changes. In fact, that's the way I initially wrote it. But there are disadvantages to that approach, including the fact that there's no way to quit the app, change any settings, or interact with it in any way. I had thought that a GUI app might use more memory or resources, but that proved to not be the case. In the end, I ended up doing this as a GUI app, though one with a minimal user interface.
...End of Excerpt. Please purchase the magazine to read the full article.
Article copyrighted by REALbasic Developer magazine. All rights reserved.