Window positioning not being read on loadup

WinEQ 2.0 Lite discussion

Moderators: Lavish Software Team, Moderators

Post Reply
EQNET
GamingTools Subscriber
Posts: 25
Joined: Wed Jul 21, 2004 6:20 pm

Window positioning not being read on loadup

Post by EQNET » Mon Nov 07, 2005 6:08 pm

As of today, WinEQ is not loading up the default window profile when I load the program and start up a profile. It used to set my display as per the settings under [Preset1] in the WinEQ.ini file. Now I have to manually press CTRL+SHIFT+1 for every session and computer to make it do what it used to. May be a side issue from the other problems that were fixed. Anyway just posting to see if others are having the same issue.

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Mon Nov 07, 2005 6:12 pm

Heh, well, technically, presets are not available to WinEQ 2 Lite users, so you're lucky it ever worked at all :) I had to break this in order to solve other problems.

What you should actually do is set the positioning in eqclient.ini instead of wineq-eq.ini.

eqclient.ini:
[Defaults]
WindowedModeXOffset=0
WindowedModeYOffset=0

pangloss
GamingTools Subscriber
Posts: 15
Joined: Sat Nov 05, 2005 11:14 am

Post by pangloss » Mon Nov 07, 2005 11:03 pm

Ok I think that may explain the problem I've been having with the pointer tip. It only happens (the pointer goes off kilter) after I execute the "Reset Window" command, which also resizes the window, lining it up with the top of the screen (which I erroneously mistook for "full screen emulation" earlier).

If I never touch the Reset Window command, the pointer problem never crops up.

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Mon Nov 07, 2005 11:13 pm

pangloss wrote:Ok I think that may explain the problem I've been having with the pointer tip. It only happens (the pointer goes off kilter) after I execute the "Reset Window" command, which also resizes the window, lining it up with the top of the screen (which I erroneously mistook for "full screen emulation" earlier).

If I never touch the Reset Window command, the pointer problem never crops up.
I changed this behavior earlier today, so that shouldnt happen anymore

Post Reply