PyKen

I will close this as electron has been updated. If the issue still persists, please open a new one.

I am not sure what you mean - if you share the rendering window, capture should continue with all its content even if you drag another window above it

that is interesting... I always have my rendering window behind all other windows and teams is still able to capture its content correctly. does this happen on other machines too?

ran into the same issue. as @dankochetov says, it should work if you add quotes `""` around the column names `name`, `processDefinitionId`, `estimateHours` as below ```ts set: { name: sql`excluded."name"`,...

Up until now, I haven't tried out FancyZones - it seems that FancyZones requires the capture window to have these properties: - focusable in order to display highlighted zones. This...

Interesting, thanks for the reference. Let me have a look the other day.

Glad you like it:) Thanks for sharing your setup! Great to hear it works with fancy zones at least with some workaround

The red border is configured as a private window and should be invisible for participants of MS teams, at least on windows. I haven't tested it on any other OS....

Private window mode probably does not work on MacOS, then :/ You can set the border size here https://github.com/mPyKen/ScreenAreaShare/blob/master/src/capture.css#L24 Let me see if I can find the time to make...

> can i set the default window position too? The app already supports parameters to set default positions for the windows. [See here](https://github.com/mPyKen/ScreenAreaShare#command-line-parameters) > what could be the reason why...