[Issue] Pop-up windows: Problem with "lack of focus" / "click out"

[needcoder]

Problem with "lack of focus". is back - when I call the "ai command" or "new prompt" then "click out." does not close the window - you need to click on this window and only then "click out" or "escape." will close it down

And sometimes the focus is triggered:
I've figured out in what cases: After I explicitly click on the window and hit "escape," - for the next window call - "click out". will work, but for subsequent times it will not work until I explicitly click on the window again and press "escape".

[nbonamy]

I am not able to find a solution for now. I have something (https://github.com/nbonamy/witsy-autolib) that works in Dev but for whatever reason does work in Production. Unable to know why.

For now I am adding a very ugly bar with close button so you can click it.

[nbonamy]

Maybe found a fix. Available in 2.0.0-rc1:
https://github.com/nbonamy/witsy/releases/tag/v2.0.0-rc1

[needcoder]

Maybe found a fix. Available in 2.0.0-rc1: https://github.com/nbonamy/witsy/releases/tag/v2.0.0-rc1

Bravo! "click out" normal works, but "ai commands" window appears again for 3-4 seconds - can we fix it?

if the speed of appearance has dropped due to calculations in which program the text is selected - it is possible to disable this in the settings

[nbonamy]

The only added delay for this is 250ms

witsy/src/main/windows/commands.ts

Line 45 in ddc770e

setTimeout(() => {

On my install which is Windows running in a virtual machine on a Mac (so far from ideal condition), I measured a delay of 50 frames on this 60fps video so 830ms total.

Screen.Recording.2025-03-07.at.08.31.53.mov

And no I am not going to add another setting.

[needcoder]

The only added delay for this is 250ms

witsy/src/main/windows/commands.ts

Line 45 in ddc770e

setTimeout(() => {
On my install which is Windows running in a virtual machine on a Mac (so far from ideal condition), I measured a delay of 50 frames on this 60fps video so 830ms total.

Screen.Recording.2025-03-07.at.08.31.53.mov
And no I am not going to add another setting.

Okay, we can write it off to the fact that I don't have a powerful hardware on my computer, but there is a fact that other windows appear very quickly and this one needs 3 seconds to appear - maybe a feature of electron

[needcoder]

maybe 250ms => 100ms

[nbonamy]

1. I don't think the 150ms difference is what you are worried about 😀
2. It is a totally arbitrary value. If this is done too early, the window stays invisible. In my tests, 250ms seems the right value but not impossible that somebody logs an issue in some time with "window does not appear".

Remember: it is a hack to mitigate an electron issue...

[nbonamy]

As predicted, had to reverse things for now. I fear this is going to end as a known-bug with no fix planned. I cannot workaround electron / OS issues.