Hi Kim,
> Yeah, I've thought about just suppressing the error...
> Don't know how easy it would be to output to the DQSD
> text field.
Are you capable of pushing javascript code or bubbling a js event at
this point?
Hmmm. That's an idea, too. What about a queue? Whadya all think of
adding a feature like a queue - basically it is a simple text file
(history.txt is the closest example) named something like queue.txt
which will run events/searches, line by line, down the file,
removing the current line as it does, when idle. This would allow us
to ignore the immediate error and instead bubble a message to the q
window. The keyhook error would be something like appending a single
line like so to the queue.txt file:
jsx document.deff.q.value = 'Cannot install keyhook';
The queue search would immediately append the following type code,
to ensure it runs again, but providing a second and a half repreive
in case the search it called was doing something:
setTimeout("queue()", 1500);
When the file is empty it still runs every second and a half or so
but doesn't do anything, 'cause there's nothing to do.
Regards,
Shawn K. Hall
http://12PointDesign.com/
http://ReliableAnswers.com/
'// ========================================================
And so, my fellow Americans, ask not what your country can
do for you; ask what you can do for your country.
-- John F. Kennedy (1917-1963)
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Archive: https://lists.sourceforge.net/lists/listinfo/dqsd-devel
