Application.idle event issue

[Muthu]

In our application, in the Application.idle event the controls are validated
and enabled. As the idle event is fired when the application queue is empty,
the validation and enabling of controls is firing continuously. This
implementation makes the system using 10% CPU processing time when 10 or more
users are using the application because most applications spend 99% of their
time in an idle state.

When I moved the control validation and enabling activity into the mouse and
keyboard events of the Mainframe class, the events are firing only keyboard
and mouse events of the Mainframe class and not always.

Can you anyone please give an alternate solution for this problem?

 

[Morten Wennevik [C# MVP]]

In our application, in the Application.idle event the controls are validated
and enabled. As the idle event is fired when the application queue is empty,
the validation and enabling of controls is firing continuously. This
implementation makes the system using 10% CPU processing time when 10 or more
users are using the application because most applications spend 99% of their
time in an idle state.

When I moved the control validation and enabling activity into the mouse and
keyboard events of the Mainframe class, the events are firing only keyboard
and mouse events of the Mainframe class and not always.

Can you anyone please give an alternate solution for this problem?

? Why would you use Application.Idle? I would consider getting notified on
Idle for tasks that should run when the user is 'away'. I may be missing
something, but control validation typically happens when you move (or attempt
to move) away from a control, or as part of a user action like clicking on a
submit-button or similar.

If you give us more detailed information regarding your application we can
give you better design suggestions.