HOW TO CUSTOMIZE CURSOR PROCESSING FULL

After processing is complete, the queue changes the cursor back to the default cursor if necessary.īelow you will find the implementation of the dispatchEvent() method for the new event queue. Then, if the event is not processed within your predetermined time limit, the timer thread changes the cursor to an hourglass. It starts the timer before dispatching an event. The new event queue contains a special timer thread for measuring the processing time for each event. You first create an event queue class that extends the standard class. But first, let's examine the solution in more detail.

HOW TO CUSTOMIZE CURSOR PROCESSING FULL

In this article, I will provide the full source code to accomplish this tip. Your queue can then measure the time it takes to process each event and change the cursor if needed. By replacing the standard event queue with your own, you can intercept every event passing through the queue. The event queue distributes every UI event that occurs in an application. The solutionīy extending the capabilities of Java's UI event dispatch queue, you can easily insert your own timing mechanism into the UI events stream. Placing code within the stream of UI events enables you to measure processing times and automate the hourglass as desired. Data modification based cursors Data modification statement based cursors Positioning based cursors Modified data reflection-based cursors Processing. Fortunately, most tasks for which you typically display the hourglass cursor are executed during the processing of user interface (UI) events. Then you simply measure the execution time and change the cursor to an hourglass when necessary. Executing the task on the actual target machine, however, lets you actively monitor how long each task takes. Judging the amount of time required to execute a given task in a development process is nearly impossible.

How to customize cursor processing