very simple dualboxing problems

[n00e1987]

i have 2 hunters at lvl 60 in wow classic,and i want to dualbox them in very simple manner,i want when i press button 1 on my frist account,to mimic it to my second account,so i dont have to press 1-alt tab-1

i watched this video https://www.youtube.com/watch?v=fa9MYt4y0dE&t=271s

and i made this in notepad

<Label alpha local SendWinM Wow1>
<Label bravo local SendWinM Wow2>
<MovementHotkey 1,2,3,4,5,6,7,8,9>
<SendLabel alpha,bravo>
<Key %Trigger%>

then i opened hotkeynet and loaded it,then i wanted to rename my two wow windows as wow1 and wow2

when i press on actions>rename a window and i press on my first wow window,it labels it WoW1 and i call it WoW1
and when i press on second window it also labels it as WoW1 but i call it WoW2
but it doesnt work
i think the program doesnt see the diference betwen my two windows,and it sees thes as same window

[Wubsie]

Heya, sorry for the late reply, but only just stumbled on this thread. Been rather busy for the last few days. The script is working fine, just tested it. From what you are saying you are calling your windows WoW1 and WoW2 while the script is looking for Wow1 Wow2. It is case sensitive, so make sure the names of the windows match exactly what you have in your script. As you pointed out yourself, this is a rather simplistic setup. You'll probably want to expand it to make your experience a lot smoother. I am also not sure why you'd want to define all your hotkeys as movement hotkeys, but I suppose it does not create a specific issue here either.

[n00e1987]

no,that is not the issue,problem si that my both wow windows r called "Wow1",so hotkeynet doesnt make difference between my 2 wow windows,it probably sees them as same window

[Wubsie]

Oh, you're renaming both your windows to Wow1?? I guess I didn't catch that from your original message. Yes, then that is definitely the issue. It will only send the keypress to the first window with that name that it finds, so each window needs an unique name.

If you're having trouble renaming the windows, I don't know why. That functionality seems to be working fine for me.