# Testing fixation window with mouse input

**URL:** https://mworks.discourse.group/t/testing-fixation-window-with-mouse-input/1008
**Category:** Support
**Created:** [July 1, 2024, 3:22am UTC](https://mworks.discourse.group/t/testing-fixation-window-with-mouse-input/1008 "2024-07-01T03:22:16Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![hokysung](https://avatars.discourse-cdn.com/v4/letter/h/ac8455/32.png) [@hokysung](https://mworks.discourse.group/u/hokysung)
#### Post date: [July 1, 2024, 3:22am UTC](https://mworks.discourse.group/t/testing-fixation-window-with-mouse-input/1008/1 "2024-07-01T03:22:17Z")

</div>

Hi,

I have a smoothly moving target fixation point and I am testing my code with mouse input to simulate the eye input. I’ve noticed if i put my mouse initially inside the trigger window, and then do nothing with the mouse (i.e. eye\_x, eye\_y will stop changing), then trigger\_flag will always remain true even when the fixation point stimulus moves away and the mouse is no longer inside the fixation window. Is this expected behavior, or is there an easy fix to this?

```auto
mouse_input eye_tracker (
    mouse_position_x = eye_x
    mouse_position_y = eye_y
    use_mirror_window = NO
    )

basic_eye_monitor (
    eyeh_calibrated = eye_x
    eyev_calibrated = eye_y
    eye_state = eyeInSaccade
    width_samples = 5
    saccade_entry_speed = 2
    saccade_exit_speed = 60
    )

```

This is my eye input simulation setup.

---

<div class="post-metadata">

### Author: ![cstawarz](https://yyz1.discourse-cdn.com/flex031/user_avatar/mworks.discourse.group/cstawarz/32/3_2.png) [@cstawarz](https://mworks.discourse.group/u/cstawarz)
#### Post date: [July 1, 2024, 2:18pm UTC](https://mworks.discourse.group/t/testing-fixation-window-with-mouse-input/1008/2 "2024-07-01T14:18:22Z")

</div>

Hi Hokyung,

Yes, this is expected behavior. The value of [trigger\_flag](https://mworks.github.io/documentation/latest/components/fixation_point_stimulus.html#trigger-flag) is updated when new values of [trigger\_watch\_x](https://mworks.github.io/documentation/latest/components/fixation_point_stimulus.html#trigger-watch-x) and [trigger\_watch\_y](https://mworks.github.io/documentation/latest/components/fixation_point_stimulus.html#trigger-watch-y) arrive. If the inputs don’t change, then neither does the output. This isn’t an issue with a real eye tracker, which updates the eye position continuously.

For testing purposes, you could use [scheduled actions](https://mworks.github.io/documentation/latest/components/schedule_actions.html) to update the eye position variables regularly from the current mouse position. Please see the attached example.

Cheers,  
Chris  
[continuous\_mouse\_input.mwel](https://mworks.discourse.group/uploads/short-url/2UGkcvdpIVyCbk9dJaJfiJMg5WW.mwel) (1.0 KB)

---

<div class="post-metadata">

### Author: ![cstawarz](https://yyz1.discourse-cdn.com/flex031/user_avatar/mworks.discourse.group/cstawarz/32/3_2.png) [@cstawarz](https://mworks.discourse.group/u/cstawarz)
#### Post date: [July 16, 2024, 1:33pm UTC](https://mworks.discourse.group/t/testing-fixation-window-with-mouse-input/1008/3 "2024-07-16T13:33:40Z")

</div>


