avatar image

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

Login with username, password and session length
  • Friday June 24, 2022, 5:56 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 - Halbyrd [ switch to compact view ]

Pages: [1]
Update: found a solution, and possibly some insight into the nature of the problem.

The way I had things set up, I had my primary display plugged into the "second" DVI port on my video card (as if these things are labeled :shrug:). GridMove apparently wasn't looking at what monitors Windows was treating as "primary", "secondary", and so on, it was looking at which physical port the display was plugged into.  Swapping the cables and restarting GM solved the problem.

Edit: Wait, no, it's still displaying this messed up behavior. I had swapped over to an unfamiliar grid, which masked the symptoms. Nothing to see here, move along...

jgpaiva: grid file is attached, though it displays this misbehavior with every grid I've tried. Basically, it acts like my monitors are flipped, so grids for monitor 1 show up on monitor 2, and grids for monitor 2 show up on monitor 1. I haven't had this problem until just recently, when I switched to a NVidia video card.  The example grid I've attached is set up for a 2x(1680x1050) desktop, side by side. I use the Win+G hotkey to relocate windows; all mouse activation is disabled in GridMove's options, so it won't conflict with Aero Snap.

Great program; it's saved me tons of hassle. One weird issue I'm running into lately though:

I run a dual widescreen setup, and have made a custom grid to suit my idiosyncratic needs. Problem is, GridMove is putting the grids for monitor 1 on monitor 2 and vice versa. I've checked and double-checked my settings; the monitors are identifying themselves correctly in the video card drivers, and Windows has them properly assigned. Is there any other reason why it would behave like this?

System details follow:
Windows 7 Enterprise 64-bit
AMD Phenom II X4 910
NVidia GeForce GTX 465, Forceware 258.96

Pages: [1]