# selectInput() anomaly

**URL:** https://discourse.processing.org/t/selectinput-anomaly/4504
**Category:** Coding Questions
**Created:** [October 15, 2018, 7:29pm UTC](https://discourse.processing.org/t/selectinput-anomaly/4504 "2018-10-15T19:29:50Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![jeremydouglass](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/jeremydouglass/32/20_2.png) [@jeremydouglass](https://discourse.processing.org/u/jeremydouglass)
#### Post date: [October 24, 2018, 8:30pm UTC](https://discourse.processing.org/t/selectinput-anomaly/4504/2 "2018-10-24T20:30:34Z")

</div>

I’m not sure – it sounds like some interaction between the callback and the event, but surprising that it is renderer-specific – that might have something to do with the difference between java.awt.Event and JOGL NEWT events – see [Back/forward/extra mouse buttons](https://discourse.processing.org/t/back-forward-extra-mouse-buttons/4515/2) – but this is beyond my ken right now. if you have documented this with a test sketch I would recommend submitting it as an issue to:

> **[processing/processing](https://github.com/processing/processing/issues/)**
>
> Source code for the Processing Core and Development Environment (PDE) - processing/processing

---

_[View the full topic](https://discourse.processing.org/t/selectinput-anomaly/4504)._