topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Thursday October 28, 2021, 1:34 pm
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - codecounselor [ switch to compact view ]

Pages: [1]
1
An update on this: After a series of undocking my computer and running without the 4k monitor, and changing the desktop scaling from 150% back to 100% everything started working as normal.  However, when I tried to apply my grid again with the desktop scaled at 100% the same problem occurred.

It seems that there is an issue with my format thats putting the entire program in a bad state that persists even during a restart.

Can anyone tell me what the problem might be?  Do I need to setup triggers as well?

2
I am hoping someone has encountered this issue before, here is whats happening...

  • I installed gridmove via chocolatey and everything was working great
  • I created a custom grid in which loaded and displayed the grid lines correctly, however it looks like it took the total resolution and somehow scaled it by 2/3, such that my laptop monitor grids are showing up on my 4k monitor.
  • I tried removing the new file and restarting GridMove
  • Then I tried uninstalling GridMove and deleting the folder under ApplicationData
  • Then I tried installing via the downloaded installer
  • The problem persists, and it affects all grids that come pre-installed

This is the config I created which seemed to cause the problem:
[Groups]

  NumberOfGroups = 7

; 4K DISPLAY

[1]
  TriggerTop    = [Monitor2Top]
  TriggerRight  = [Monitor2Left] + [Monitor2Width]  /3
  TriggerBottom = [Monitor2Top]  + [Monitor2Height] * 2/3
  TriggerLeft   = [Monitor2Left]

[2]

  TriggerTop    = [Monitor2Top]
  TriggerRight  = [Monitor2Right]
  TriggerBottom = [Monitor2Top]  + [Monitor2Height] * 2/3
  TriggerLeft   = [Monitor2Left] + [Monitor2Width]  /3

[3]

  TriggerTop    = [Monitor2Top]  + [Monitor2Height] * 2/3
  TriggerRight  = [Monitor2Left] + [Monitor2Width]  /3
  TriggerBottom = [Monitor2Bottom]
  TriggerLeft   = [Monitor2Left]

[4]

  TriggerTop    = [Monitor2Top]  + [Monitor2Height] * 2/3
  TriggerRight  = [Monitor2Right]
  TriggerBottom = [Monitor2Bottom]
  TriggerLeft   = [Monitor2Left] + [Monitor2Width]  /3

; LAPTOP MONITOR

[5]

  TriggerTop    = [Monitor1Top]
  TriggerRight  = [Monitor1Left] + 400
  TriggerBottom = [Monitor1Bottom]
  TriggerLeft   = [Monitor1Left]

[6]

  TriggerTop    = [Monitor1Top]
  TriggerRight  = [Monitor1Right]
  TriggerBottom = [Monitor1Top]  + [Monitor1Height] /2
  TriggerLeft   = [Monitor1Left] + 400

[7]

  TriggerTop    = [Monitor1Top]  + [Monitor1Height] /2
  TriggerRight  = [Monitor1Right]
  TriggerBottom = [Monitor1Bottom]
  TriggerLeft   = [Monitor1Left] + 400


I believe I also had done this initially instead of multiplying by 2/3
  TriggerTop    = [Monitor2Bottom]  - [Monitor2Height] /3

Here is a screenshot of the upper left grid in the 4-part template, showing the actual size of the sublime editor:
GridMove.PNG

Pages: [1]