Close
Page 1 of 2 1 2 LastLast
Showing results 1 to 10 of 13
  1. #1

    Default Wow windows AutoFit

    Hi all, for now I am a newbie to all this and above me English is bad. Luckily we have google.

    At issue in cuention. Looking HotkeyNet Guides I found the basic script 2 windows for 1 pc.

    Copy & paste:

    / / ------------------------------------------------ ----------------
    / / SET PIP CONFIGURATION
    / / Usage: <SetPip BigWindowName LittleWindowName>
    / / This command is called by <Hotkey F1> Which is defined below.
    / / ------------------------------------------------ ----------------
    <Command SetPip>
    <TargetWin %2%>
    <SetWinSize 400 300>
    1270 <SetWinPos 740>
    <TargetWin %1%>
    <SetWinPos 0 0>
    1680 <SetWinSize 1050>
    <TargetWin %2%>
    <SetForegroundWin>
    <UpdateWin>
    <TargetWin %1%>
    1270 740 400 300> <SetWinRegion
    <SetForegroundWin>

    / / ------------------------------------------------ ----------------
    / / TOGGLE PIP CONFIG WITH HOTKEY
    / / ------------------------------------------------ ----------------
    ScrollLockOn <Hotkey F1>
    <Toggle>
    Wow2 <SetPip WoW1>
    <Toggle>
    WoW1 <SetPip WoW2>


    The good thing about all this is that. is working! The bad thing is not my resolution and do not know how to put it to put everything in place.

    My screen resolution is 1920x1080. But if I put it in the taskbar "windows 7" eats a display portion, and wow small window I do not get put in the corner.

    Plz a little help. Thanks ^ ^

  2. #2

    Default

    Good news is it's not too difficult to change the script for your needs. Just describe as best you can want you want it to look like and the size of the small window(s). Even a poorly drawn paint picture can help. And I can change what you need. On a side note do you want the taskbar to show or is it something you would rather hide?

  3. #3

    Default

    Thanks for responding so quickly.

    The problem is I do not know what resolution to put in the small window, the position would be the bottom right corner of the screen. 400 300 is the one I have now and it's something small.

    The taskbar I would like to stay behind the wow, but if I can not make it work I end up hiding. His position is the normal (below)

    Sorry, that is not well written and certainly the tenses do not correspond.

    Thanks for the help.

    P.D: Any site where I can upload the img. Or does not matter?

    img => http://s2.subirimagenes.com/otros/pr...2pantallas.jpg
    Attached Images Attached Images    
    Last edited by nonayn0 : 10-16-2012 at 02:15 PM Reason: Add img

  4. #4

    Default

    The windows task bar is about 20px, so you just need to chop off a few pixels from the size. I use 1920x1050. If you are doing 2 on one monitor, you will also need to size down the width to fit the other window, or you will need to use Picture in Picture.

    The script you listed is all sorts of wrong in formatting. There's tons of stuff that's not in brackets like it's supposed to be.

    Code:
    1270 <SetWinPos 740>
    No idea what the 1270 outside the brackets is supposed to be and you don't have a second set of numbers in the brackets, so you don't have a location for the window to go.

    Code:
    1680 <SetWinSize 1050>
    Again, numbers outside the brackets and an incomplete number set inside, so you don't have a window size established.

    Code:
    1270 740 400 300> <SetWinRegion
    Missing brackets again and there's no definition for those numbers, so they aren't doing anything.

    Code:
    ScrollLockOn <Hotkey F1>
     <Toggle>
     Wow2 <SetPip WoW1>
     <Toggle>
     WoW1 <SetPip WoW2>
    More stuff outside the brackets. You don't have the hotkey properly defined and you don't have an order defined in the toggle.

    This is what a PiP code should look like


    Code:
    //----------------------------------------------------------------
     // SET PIP CONFIGURATION
     // Usage: <SetPip BigWindowName LittleWindowName>
     // This command is called by <Hotkey F1> which is defined below. 
     //----------------------------------------------------------------
     <Command SetPip>
        <TargetWin %2%>
           <SetWinSize 400 300>
           <SetWinPos 775 515>
        <TargetWin %1%>
           <SetWinPos 0 0>
           <SetWinSize 1200 900>
        <TargetWin %2%>
           <SetForegroundWin>
           <UpdateWin>
        <TargetWin %1%>
           <SetWinRegion 775 515 400 300>
           <SetForegroundWin>
    
     //----------------------------------------------------------------
     // TOGGLE PIP CONFIG WITH HOTKEY
     //----------------------------------------------------------------
     <Hotkey ScrollLockOn F1>
        <Toggle>
           <SetPip WoW1 WoW2>
        <Toggle>
           <SetPip WoW2 WoW1>

    Nothing is defined outside of the brackets except the code comments. Every number should come in at least a set -

    SetWinSize needs a number for Height and a number for Width {ex 400 300 says "make the referenced window 400 pixels wide and 300 pixels high"}

    SetWinPos needs a number for number of pixels from the top of the screen and a number for number of pixels from the left side of the screen {ex 775 515 says "put the referenced window's top-left corner at 775 pixels from the left side of the screen and 515 pixels from the top of the screen."}


    SetWinRegion needs both sets of numbers to define the size of the hole to punch and the position in which to put the hole {ex 775 515 400 300 says "at 775 pixels from the left side of the screen and 515 pixels from the top of the screen, make a hole that is 400 pixels wide by 300 pixels high".


    Take a look at my HotKeyNet starter script guide. The Refining Your Script section goes over how to lay out windows and such.
    Blog : Herding Khats
    Team : Kina - Çroaker - Messkit - Lìfetaker - Wìdowmaker
    Newbie Guides : Multiboxing Vol. 1 - Multiboxing Vol. 2 - HotKeyNet - Jamba
    The Almighty Lax made a liar out of me, apparently I DO get prizes for it.
    *Commences Wielding the Banhammer like there's piñatas up in here and I'm Lady Thor*

    _ Forum search letting you down? Use the custom Google search _

  5. #5

    Default

    Quote Originally Posted by Khatovar View Post
    The windows task bar is about 20px, so you just need to chop off a few pixels from the size. I use 1920x1050. If you are doing 2 on one monitor, you will also need to size down the width to fit the other window, or you will need to use Picture in Picture.

    The script you listed is all sorts of wrong in formatting. There's tons of stuff that's not in brackets like it's supposed to be.

    Code:
    1270 <SetWinPos 740>
    No idea what the 1270 outside the brackets is supposed to be and you don't have a second set of numbers in the brackets, so you don't have a location for the window to go.

    Code:
    1680 <SetWinSize 1050>
    Again, numbers outside the brackets and an incomplete number set inside, so you don't have a window size established.

    Code:
    1270 740 400 300> <SetWinRegion
    Missing brackets again and there's no definition for those numbers, so they aren't doing anything.

    Code:
    ScrollLockOn <Hotkey F1>
     <Toggle>
     Wow2 <SetPip WoW1>
     <Toggle>
     WoW1 <SetPip WoW2>
    More stuff outside the brackets. You don't have the hotkey properly defined and you don't have an order defined in the toggle.

    This is what a PiP code should look like


    Code:
    //----------------------------------------------------------------
     // SET PIP CONFIGURATION
     // Usage: <SetPip BigWindowName LittleWindowName>
     // This command is called by <Hotkey F1> which is defined below. 
     //----------------------------------------------------------------
     <Command SetPip>
        <TargetWin %2%>
           <SetWinSize 400 300>
           <SetWinPos 775 515>
        <TargetWin %1%>
           <SetWinPos 0 0>
           <SetWinSize 1200 900>
        <TargetWin %2%>
           <SetForegroundWin>
           <UpdateWin>
        <TargetWin %1%>
           <SetWinRegion 775 515 400 300>
           <SetForegroundWin>
    
     //----------------------------------------------------------------
     // TOGGLE PIP CONFIG WITH HOTKEY
     //----------------------------------------------------------------
     <Hotkey ScrollLockOn F1>
        <Toggle>
           <SetPip WoW1 WoW2>
        <Toggle>
           <SetPip WoW2 WoW1>

    Nothing is defined outside of the brackets except the code comments. Every number should come in at least a set -

    SetWinSize needs a number for Height and a number for Width {ex 400 300 says "make the referenced window 400 pixels wide and 300 pixels high"}

    SetWinPos needs a number for number of pixels from the top of the screen and a number for number of pixels from the left side of the screen {ex 775 515 says "put the referenced window's top-left corner at 775 pixels from the left side of the screen and 515 pixels from the top of the screen."}


    SetWinRegion needs both sets of numbers to define the size of the hole to punch and the position in which to put the hole {ex 775 515 400 300 says "at 775 pixels from the left side of the screen and 515 pixels from the top of the screen, make a hole that is 400 pixels wide by 300 pixels high".


    Take a look at my HotKeyNet starter script guide. The Refining Your Script section goes over how to lay out windows and such.
    awesome ...

    I just did a copy & paste from another post, the truth is that you do not quite understand the scrip. You could wear it with resolution of 1920x1080?

    It is asking that you get chewed things, but I have no knowledge of how to do it myself haha.

    Tonight at home I start to read your guide and maybe soon begins to play a good resolution.

  6. #6

    Default

    Wow Khat you are really fast... Anyway if you don't want to see the taskbar HKN has a function for hiding it, I usually put this with my toggle hotkeys hotkey. It helps me see when HKN is disabled vs enabled.

    The following code is slightly modified from what Khat already posted.

    Code:
    //---------------------------------------------------------------- 
    // SET PIP CONFIGURATION  
    // Usage: <SetPip BigWindowName LittleWindowName>  
    // This command is called by <Hotkey F1> which is defined below.   
    //----------------------------------------------------------------  
    <Command SetPip>     
    <TargetWin %2%>
            <SetWinSize 384 216>
            <SetWinPos 1536 864>
         <TargetWin %1%>
            <SetWinPos 0 0>
            <SetWinSize 1920 1080>
         <TargetWin %2%>
            <SetForegroundWin>
            <UpdateWin>
         <TargetWin %1%>
            <SetWinRegion 1536 864 384 216>
            <SetForegroundWin>   
    //----------------------------------------------------------------  
    // TOGGLE PIP CONFIG WITH HOTKEY 
    //----------------------------------------------------------------  
    <Hotkey ScrollLockOn F1>
         <Toggle>
            <SetPip WoW1 WoW2>
         <Toggle>
            <SetPip WoW2 WoW1>
    //----------------------------------------------------------------  
    // TOGGLE HOTKEYS AND TASKBAR Oem3 types the ~ (tilde) or ` (grave) character on most keyboards
    //----------------------------------------------------------------  
    <Hotkey Oem3>
       <SetTaskbarAutoHide toggle>
       <ToggleHotkeys>
    I colored the text that you may need to change. Green is the width and height of the small window, you will have to change the numbers to match in both places colored green. The orange numbers will position the window and cutout in the lower right corner of the screen. This could possibly overlap elements of the game so you may need to adjust it a bit. The reason for the weird (non-100 multiples) numbers is to maintain resolution of the small window and speed up switches, they should be instant if you maintain percentages of the main resolution, in this case I used 20%.

    The blue numbers make the main window fullscreen.

    NOTE :::: If you want to see the taskbar while playing you will have to shrink the height to about 1060, switch both 216's to 212's, and both 864's to 844's. You will also need to remove the <SetTaskbarAutoHide toggle> command. ::::

    If you can't figure out what you need to change post your complete script inside CODE tags, and I'm sure everything can be worked out. Remember to remove login information such as usernames and passwords if you post the full script.

  7. #7

    Default

    Final result:

    / / ------------------------------------------------ ----------------
    / / SET PIP CONFIGURATION
    / / Usage: <SetPip BigWindowName LittleWindowName>
    / / This command is called by <Hotkey F1> Which is defined below.
    / / ------------------------------------------------ ----------------
    <Command SetPip>
    <TargetWin %2%>
    470 <SetWinSize 360>
    1450 <SetWinPos 725>
    <TargetWin %1%>
    <SetWinPos 0 0>
    1920 <SetWinSize 1080>
    <TargetWin %2%>
    <SetForegroundWin>
    <UpdateWin>
    <TargetWin %1%>
    <SetWinRegion 360> 1450 725 470
    <SetForegroundWin>

    / / ------------------------------------------------ ----------------
    / / TOGGLE PIP CONFIG WITH HOTKEY
    / / ------------------------------------------------ ----------------
    ScrollLockOn <Hotkey F1>
    <Toggle>
    WoW1 <SetPip WoW2>
    <Toggle>
    Wow2 <SetPip WoW1>

    The small window resolution is something ... Strange. There is nothing wrong about this?

    Thanks for the responses, Bettysue are great!

    PS: The Windows taskbar is no longer a problem ^ ^

  8. #8

    Default

    You still have information outside the brackets. And we're going to need something more than "strange" to troubleshoot.

    Code:
    / / ------------------------------------------------ ----------------
     / / SET PIP CONFIGURATION
     / / Usage: <SetPip BigWindowName LittleWindowName>
     / / This command is called by <Hotkey F1> Which is defined below.
     / / ------------------------------------------------ ----------------
    <Command SetPip>
     <TargetWin %2%>
      <SetWinSize 470 360>
      <SetWinPos 1450 725>
     <TargetWin %1%>
      <SetWinPos 0 0>
      <SetWinSize 1920 1080>
     <TargetWin %2%>
      <SetForegroundWin>
      <UpdateWin>
     <TargetWin %1%>
      <SetWinRegion 360 1450 725 470>
      <SetForegroundWin>
    
     / / ------------------------------------------------ ----------------
     / / TOGGLE PIP CONFIG WITH HOTKEY
     / / ------------------------------------------------ ----------------
    <Hotkey ScrollLockOn F1>
     <Toggle>
      <SetPip WoW1 WoW2>
     <Toggle>
      <SetPip WoW2 WoW1>
    Last edited by Khatovar : 10-17-2012 at 05:46 AM
    Blog : Herding Khats
    Team : Kina - Çroaker - Messkit - Lìfetaker - Wìdowmaker
    Newbie Guides : Multiboxing Vol. 1 - Multiboxing Vol. 2 - HotKeyNet - Jamba
    The Almighty Lax made a liar out of me, apparently I DO get prizes for it.
    *Commences Wielding the Banhammer like there's piñatas up in here and I'm Lady Thor*

    _ Forum search letting you down? Use the custom Google search _

  9. #9

    Default

    Something seems to be destroying the formatting of your posted scripts, so I'm guessing here, and is appears Khat came to the same conclusion on where you are trying to go.

    It looks like you want the small window to be 33% of the large window at 360 pixels high. To maintain resolution it needs to be 640 pixels (1920*0.3333...) wide.

    The following has the resolution set that way.

    Code:
    //----------------------------------------------------------------  
    // SET PIP CONFIGURATION   
    // Usage: <SetPip BigWindowName LittleWindowName>   
    // This command is called by <Hotkey F1> which is defined below.    
    //----------------------------------------------------------------   
    <Command SetPip>
          <TargetWin %2%>
             <SetWinSize 640 360>
             <SetWinPos 1280 720>
          <TargetWin %1%>
             <SetWinPos 0 0>
             <SetWinSize 1920 1080>
          <TargetWin %2%>
             <SetForegroundWin>
             <UpdateWin>
          <TargetWin %1%>
             <SetWinRegion 1280 720 640 360>
             <SetForegroundWin>

  10. #10

    Default

    Quote Originally Posted by Bettysue View Post
    Khat came to the same conclusion on where you are trying to go.


    The following has the resolution set that way.

    Code:
    //----------------------------------------------------------------  
    // SET PIP CONFIGURATION   
    // Usage: <SetPip BigWindowName LittleWindowName>   
    // This command is called by <Hotkey F1> which is defined below.    
    //----------------------------------------------------------------   
    <Command SetPip>
          <TargetWin %2%>
             <SetWinSize 640 360>
             <SetWinPos 1280 720>
          <TargetWin %1%>
             <SetWinPos 0 0>
             <SetWinSize 1920 1080>
          <TargetWin %2%>
             <SetForegroundWin>
             <UpdateWin>
          <TargetWin %1%>
             <SetWinRegion 1280 720 640 360>
             <SetForegroundWin>
    yeah, sorry. I did not communicate well in English. Google translator is not a panacea.

    I'll try your script. I like this running around and I hope to start playing.

    Changing the subject of screens wow, as I get that space make up the flying mount? Or when I am diving up the pj?

    Currently the pj jumping, but flying mounts or water does not seem to work. I guess because the HKN only send 1 pulse and not one maintained. This can be fixed?

    Thank you very much! You are helping me a lot!

    Maybe something like this?
    Code:
    //-----------------------------------------------------------
    // DEFINE MOVEMENT KEYS THAT WILL GET SENT TO BOTH WOW'S.
    // ADD MORE KEYS IF YOU WANT.
    //-----------------------------------------------------------
    <MovementHotkey ScrollLockOn up, down, left, right, space>
    <SendLabel w1, w2>
    <Key %Trigger%>
    Last edited by nonayn0 : 10-19-2012 at 06:00 AM

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •