Possible new bug, or just me being a donkey?

[Knytestorme]

As an update to this it seems to only be affecting regions 1 and 2. Regions 3 and 4 go directly to the bottom quarters of the screen as expected so I'm going to delete the ini file and redo it tonight to see if there may be a hidden region somewhere in there. Will let you know how it goes.

[EDIT]

Sorry, forgot to add an answer to your questions.

Compatability mode is unchecked
Advanced text services I'll have to recheck when I get home.

[Knytestorme]

Well PiP and BOOBS is now back working after I deleted the .ini and recreated my maximizer details. The new ini is

[general]
version=1806
port=1320
name=dante
boost_performance=0
auto_add=0,0,'World of Warcraft'
auto_add_keymap=0,''
auto_connect=0,''
pass_mouse_clicks=0
send_only=0
distinguish_lr=0
maximizer_enabled=1
always_on_top=0
proxy_enabled=0
proxy=
proxy_uname=
has_startup_cmd=0
startup_cmd=
startup_cmd_delay=5
hotkey_bringtofront=0.0
mousefocus=0

[donotpass]
whitelist=0
count=10
key_00=13.0
key_01=65.0
key_02=66.0
key_03=67.0
key_04=68.0
key_05=76.0
key_06=78.0
key_07=83.0
key_08=87.0
key_09=191.0

[roundrobin]
count=0

[commands]
count=5
command_00=account
action_00=D:\Games\WoWIva\Wow.exe
keymap_00=
region_00=region1
uname_00=1.'account'
cpu_00=00000001
maxfps_00=45.15
excludeRR_00=0
alwaysOnTop_00=1
lockInForeground_00=1
command_01=account2
action_01=D:\Games\WoWBaan\Wow.exe
keymap_01=
region_01=region3
uname_01=1.'account2'
cpu_01=00000002
maxfps_01=45.15
excludeRR_01=0
alwaysOnTop_01=1
lockInForeground_01=1
command_02=account3
action_02=D:\Games\WoWSmar\Wow.exe
keymap_02=
region_02=region0
uname_02=1.'account3'
cpu_02=10000000
maxfps_02=60.15
excludeRR_02=0
alwaysOnTop_02=1
lockInForeground_02=1
command_03=account4
action_03=D:\Games\WoWNuaa\Wow.exe
keymap_03=
region_03=region2
uname_03=1.'account4'
cpu_03=00000004
maxfps_03=45.15
excludeRR_03=0
alwaysOnTop_03=1
lockInForeground_03=1
command_04=account5
action_04=D:\Games\WoWCall\Wow.exe
keymap_04=
region_04=region4
uname_04=1.'account5'
cpu_04=00000008
maxfps_04=45.15
excludeRR_04=0
alwaysOnTop_04=1
lockInForeground_04=1

[mousemap]
count=0

[regions]
count=5
region_name_00='region0'
region_00=1,0,0,1679,1048,0,0
region_pip_00=0,(117.0.0)
region_name_01='region1'
region_01=1,0,0,840,524,1,0
region_pip_01=0,(118.0.0)
region_name_02='region2'
region_02=1,840,0,1679,524,1,0
region_pip_02=0,(119.0.0)
region_name_03='region3'
region_03=1,0,524,840,1048,1,0
region_pip_03=0,(120.0.0)
region_name_04='region4'
region_04=1,840,524,1679,1048,1,0
region_pip_04=0,(121.0.0)

[cmd_history]
count=5
cmd_00=account
cmd_01=account2
cmd_02=account4
cmd_03=account5
cmd_04=account3
last=account3

[override]
hotkey=19.0
hotkey2=0.0
suspend_hotkey=0.0
dnp_hotkey=33.0
rr_hotkey=0.0
enable_overlays=1
enable_audio_reminder=0
reminder_delay=20
message=mute
font_name=tahoma
font_sz=30
font_color=20.200.0

[sounds]
count=6
sound_00=1001,1,'D:\Games\keyclone\sounds\open.wav'
sound_01=1002,1,'D:\Games\keyclone\sounds\close.wav'
sound_02=1003,1,'D:\Games\keyclone\sounds\override_on.wav'
sound_03=1004,1,'D:\Games\keyclone\sounds\override_off.wav'
sound_04=1005,1,'D:\Games\keyclone\sounds\override_reminder.wav'
sound_05=1006,1,'D:\Games\keyclone\sounds\roundrobin.wav'

I think you were right about something still conflicting though Keyclone. I still have to start and then close accounts 1 and 4 to have them appear in the correct regions, and tonight I noticed something stranger. I had accounts 1,2,4,5 up in there regions and fired up account 3 (the main screen) and noticed that muting and over-riding the dnp list hotkeys weren't working. When I closed that account down and restarted it they were working, in much the same way the accounts going into the regions need to be opened, closed, reopened to work correctly.

I've checked to make sure I don't have another instance of keyclone open and hidden away somewhere by looking at all processes currently running, so I'm not sure what it could be at this stage. It's not game-breaking, more of a slight inconvenience on startup as after that it works as well as expected, but would be nice to track down what it oculd be.

[Knytestorme]

Ok, spent a few hours in vent tonight with KC and seems we have tracked the cause of the problem donw. Once I unchecked the fullscreen and maimized tickboxes in the WoW client video interface everything worked as expected, so if you have the same issue go do that