Close
Showing results 1 to 10 of 13

Hybrid View

  1. #1

    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 _

  2. #2

    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.

Posting Rules

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