Home/ Questions/Q 112173
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T02:30:11+00:00

I have a JFace editor that is mostly made up of a TreeViewer .

  • 0

I have a JFace editor that is mostly made up of a TreeViewer. This is hooked up to a ContentOutlinePage to bring the Outline view to life.

When either one receives a SelectionChangedEvent they call the others setSelection() method … and therein lies the problem. setSelection() generates another SelectionChangedEvent … and thus the infinite loop is joined.

Is there a means of telling if the SelectionChangedEvent was created by actual user interaction rather than by another object calling setSelection()?

Is there a better means still of stopping this sort of deadly-embrace?

Clues welcomed.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Generally, you would check a flag in the beginning of the routine to check to see if you are in the middle of the event handler. If the flag is set, then you exit without processing.

    If the flag is not set, you set the flag, process, then set the flag back.

    • 0