I'm sorry, can you revert my proposed fix? It breaks other behaviour, like mouse switching between windows.

Apologies, I will fix that issue properly later

Apart from that, everything is ok

pls note i had to run npm audit fix and npm update otherwise the builds were failing with ERR_OSSL_EVP_UNSUPPORTED

I'm sorry, can you revert my proposed fix? It breaks other behaviour, like mouse switching between windows.

Apologies, I will fix that issue properly later

Could we fix it using always the same grid when showGridOnAllMonitors is false?
In app.ts we could change CurrentGrid() to this:

  public get CurrentGrid(): Grid {
    if (!this.config.showGridOnAllMonitors) {
      return this.grids[0];
    }
    const grid = this.grids.find(x => x.monitor.index == this.currentMonitor.index)!;
    return grid;
  }

Edit:
We should also update the lines you referred to as follows

    if (!this.config.showGridOnAllMonitors) {
      if (this.CurrentGrid) {
        this.CurrentGrid.ChangeCurrentMonitor(this.monitors[this.focusMetaWindow.get_monitor()]);
      }
    }

Had a bit of time to look today, the problem is that the function is executed twice, here first:

https://github.com/settenop/cinnamon-spices-extensions/blob/master/gTile%40shuairan/src/base/app.ts#L120-L121

So these 2 lines can be removed. Of course a null check would definitely help, even tho CurrentGrid should never be null

yes, I've found some issues too.

• the hover in the grid elements are triggered even if the mouse hover the grid because the grid is moving while the mouse don't (for example when !this.config.showGridOnAllMonitors).
• when the mouse is used to move the grid to another monitor by clicking on a free desktop area nemo is selected as the target application.
• while the grid is opened changing focus to another window of the same application will not change the target window. (fixed in f6ca8f3)

@Gr3q Any update on merging this? Would really like to use gTile with my terminal :D

@brownsr is the one who reviews and merges PRs

My bad @Gr3q , Figured you were the one to ask as you are set as Reviewer on the PR

@brownsr You think you can take a look and merge the branch soon :D ?

Sorry for the long wait, I hadn't seen there was a change waiting here. Unfortunately there are conflicts. Can you resolve these, and then I should be able to merge.

Regards

Simon

@settenop This PR is now too old. Please create a new one after synchronizing your master branch fork.