The ban on multiple triggering events when operating with the mouse

Good day to all!

I write my own GUI-interface for the toy.

Class Button .

There is the following set of delegate events:

 public event EventHandler MouseUpHandler; public event EventHandler MouseDownHandler; public event EventHandler MouseOutHandler; public event EventHandler MouseInHandler; 

Each event has its own method:

 private void OnMouseIn() {...} private void OnMouseOut() {...} private void OnMouseUp() {...} private void OnMouseDown() {...} 

They run something like this:

 private void OnMouseDown() { EventHandler tempHandler = MouseDownHandler; // получаем делегат события if (tempHandler != null) // проверяем, не пустой ли делегат { tempHandler(this, EventArgs.Empty); // вызываем событие } _state = ButtonState.Click; // используется для определения правильных координат на спрайте текстуры кнопки во время ее рисования } 

Appropriate methods are present for other delegate events. In the same class, there is the Update() method, which calculates the logic of the code:

 public void Update() { /* Формируем данные о положении мыши и о зоне пересечения (на основе позиции и размеров кнопки) */ MouseState mouseState = Mouse.GetState(); Point mousePosition = new Point(mouseState.X, mouseState.Y); Rectangle buttonRectangle = new Rectangle ( (int) this.Position.X, (int) this.Position.Y, (int) this.Size.X, (int) this.Size.Y ); if (buttonRectangle.Contains(mousePosition)) // проверяем на наличие пересечения курсора мыши и кнопки { if (mouseState.LeftButton == Microsoft.Xna.Framework.Input.ButtonState.Pressed) //ЛКМ - нажатие кнопки мыши { OnMouseDown(); } if (_mousePrevState.LeftButton == Microsoft.Xna.Framework.Input.ButtonState.Pressed && mouseState.LeftButton == Microsoft.Xna.Framework.Input.ButtonState.Released) // ЛКМ - отпускание кнопки мыши { OnMouseUp(); } } else // выход курсора за границы кнопки { OnMouseOut(); } _mousePrevState = mouseState; // сохраняем предыдущее состояние (MouseUp может быть только после MouseDown) } 

In another place an instance of the button is created:

 Button button = new Button(...); 

Respectively properties, textures, etc. are set. It all works. Further, in the same "other place", the delegate is assigned a method:

 button.MouseInHandler += Название_метода; 

With this, I think everything should be clear. The logic is briefly - an object is created, a method is assigned to it in a special delegate, after which the Update() method checks if the button and cursor intersection, clicked, etc. and based on this, the event we need is already triggered.

The problem that exists now: the method is called not once, but many times in a row.

All this leads to the fact that, for example, the output to the console of any text occurs many times, but no more than one is required.

I tried to solve the problem using additional fields:

 private bool _isMouseUp; private bool _isMouseDown; private bool _isMouseIn; private bool _isMouseOut; 

With a change in the logic structure of event methods

 private void OnMouseIn() { if (!_isMouseIn) // если событие не вызывалось { EventHandler tempHandler = MouseInHandler; if (tempHandler != null) { tempHandler(this, EventArgs.Empty); } _isMouseIn = true; // определяем событие, как вызванное и не даем ему совершиться повторно _isMouseOut = false; // после In события можно допустить выполнение Out события } _state = ButtonState.Hover; } // примерно такой же код ниже, разве что теперь Out и In поменялись местами private void OnMouseOut() { if (!_isMouseOut) { EventHandler tempHandler = MouseOutHandler; if (tempHandler != null) { tempHandler(this, EventArgs.Empty); } _isMouseOut = true; _isMouseIn = false; } _state = ButtonState.Normal; } 

For MouseDown and MouseUp corresponding changes.

And it all works, as long as the user behaves normally. However, if you try different situations, for example, hold the paint button, then move the button and release, or hold the paint button over the button and release it in another place - all this leads to the fact that at some point an event that should it was to be called - not called, or vice versa, that event is raised, which should not be called.

I tried to describe my problem in as much detail as possible, but if there are any questions, ask, clarify if necessary.