We will take a look at this right away. If it's as serious as you say
then this is a P1 issue.
-- Kevin
Chris Nahr wrote:
Yes, I can confirm this bug is present when running on a Dell XPS 15
which does have both a touchscreen and an integrated Intel GPU for
desktop display (HD 4600). The
Thanks for looking into this.
Although, I don't believe Intel graphics card have anything to do with this
bug, unlike the reports on Stack Overflow. I tested with both AMD and
Nvidia cards, and the only factor seemed to be if my touchscreen was
plugged in or not on my desktop computer.
Cheers
Thanks, I very much appreciate it!
> On 15 Sep 2015, at 18:53, Kevin Rushforth wrote:
>
> We will take a look at this right away. If it's as serious as you say then
> this is a P1 issue.
>
> -- Kevin
>
>
> Chris Nahr wrote:
>> Yes, I can confirm this bug is
Hi,
this workaround works fine for my use cases where accessibility is not an
issue.
I added it to all shortcuts / batch files and all combo boxes work fine. I
tested with and without the requestFocus workaround for the mouse and it
does not interfere.
Thank you for the quick find!
It is still
Thanks for confirming it. Another workaround for those who need
accessibility is to turn Windows Narrator on before clicking on any
combobox. That also seems to avoid the bug. I put both workarounds in
the bug report.
-- Kevin
Guillaume Anctil wrote:
Hi,
this workaround works fine for my
Yes, I can confirm this bug is present when running on a Dell XPS 15
which does have both a touchscreen and an integrated Intel GPU for
desktop display (HD 4600). The application hangs even though I'm using a
mouse and not the touchscreen to click on the combo box.
That's a catastrophic bug