spawn_on_current_workspace does not work for eclipse-based applications

[wilriker]

Steps to reproduce

1. Install an eclipse-based application (I used dbeaver)
2. Select workspace 1
3. Start dbeaver using any of the "spawn on workspace" methods
4. Quickly select workspace 2

Observed behavior

After a few seconds the main window of dbeaver will map on workspace 2.

Expected behavior

dbeaver's main window should appear on workspace 1.

Assumed cause

dbeaver like most of eclipse-based applications has a splash-screen. This in turn is rendered on workspace 1. But that will fork again into the main window. But since the PendingSpawn rule has already been handled and discarded the fork will then be mapped to selws at the time it does appear.

[wegel]

Hmm. I would like to avoid trying to track spawned windows over time or anything like that. Did you try eg dbeaver -nosplash ?

[wilriker]

I just tried it with -nosplash but that had the same behavior. dbeaver main window eventually appeared on selws independent on what I told it on which workspace it should spawn.

It does work though for all other applications I have used so far.

As a solution I was thinking about the following: you already have a timeout on the spawn-on-rules. Why not keep the rule around and apply it until the timeout is reached instead of discarding it after first application of the rule? I might try this later.

[wilriker]

So, I finally tried keeping the spawn rules around until they expire (actually until the next time after expiry a rule is being claimed) instead of removing them immediately after first usage and that solves the issue for dbeaver.

Maybe with the addition of wiring out the timeout duration into config that could be a viable solution (at least to me it would be).