Hey all - for a long time now, people have been asking about my Stick Online HotKeyz, and I've really appreciated the enthusiasm. However, SO went down shortly after their release, so I never updated them. However, just recently Seifer brought it up again, and I finally sat down and completely rewrote the entire thing.
I last left it off with a terribly long executable shortcut name, SOHKV1.00BETA - seeing as that implies it was in beta, I'm pulling it out of beta, and this is Stick Online HotKeyz v1.01 (Now v1.03). Below I'll just put all of the highlights, then I'll explain them as I go on.
Update: v1.03 has been released - this adds FULL SCREEN SUPPORT ;D
I'd like to thank ARTGames and Lingus especially - they provided me with the math and the motivation. Thank you guys!
Change Log -
Changes from v1.02 to v1.03:
[New Feature] Fullscreen is now supported!
[Improvement] Various small improvements and fixes
Changes from v1.01 to v1.02:
[Fix] Delay function now works correctly for all slots and hot keys
Changes from v1.00 BETA to v1.01:
[New Feature] Delay, which allows you to set the speed at which it switches
[Improvement] On startup, automatically loads settings and sets them
[Improvement] Automatically refreshes hotkeys every time they are saved or loaded - the Refresh button is now removed
[Improvement] Improved performance and memory usage (all leaks removed, and a large reduction in memory usage)
[Improvement] It is now possible to map the most keys on your keyboard (Function keys, Numpad, etc)) in HKSettings.ini (Read on for explanation)
[Fix] You can now exit Hotkeyz even when HotKeyz is paused
[Fix] It will no longer queue up actions and perform them after paused (happened on rare occasions)
[Fix] Stick Online must be active for hotkeys to activate - The program will no longer automatically bring up Stick Online when you press a Hotkey while the program is not paused
Known Bugs/Features to be Implemented:
Cannot type unless HotKeyz is paused
For new users, please read the Read Me included in the zip folder, and also take a look at the 'Options > Controls' within the program itself. Read on if you want too, as well.
DOWNLOAD V1.03 HERE: Download SOHK (http://v2info.stick-league.com/)
Phew, okay. As I said, I completely rewrote it so that the program runs much smoother and faster, and takes up much less memory (not to mention, I removed a large memory leak). But here is some explanations for the things above.
First, the new addition of Delay. At the top of the GUI, you can now change the delay in which the hats switch when you press a hotkey. I recommend 20, as it seems to work on most computers. However, for slower computers, or just those having a problem with the speed, you can increase the number to slow down the speed. 100 is pretty slow, so I'd recommend trying things between 20 and 100. Do not go below 20, thats too fast, and it will more than likely miss switching your items, and it may leave the inventory out.
The other improvement is that I removed the 'Refresh' button - now, the program automatically sets the hotkeys whenever you save or load, and on start up. Additionally, it loads the hotkeys on start up. So every time you change the hotkeys or slot, save it, and it will refresh.
The other big thing, is that now you can edit the HKSettings.ini file located within the same folder as SOHK.exe, and put in hotkeys for F2 through F12, the Numpad, or other special characters on your keyboard. To do so, follow this example:
[HotKeys]
Hotkey1={F2}
Hotkey2={NUMPAD1}
Hotkey3={NUMPADADD}
Hotkey4={END}
Hotkey5={HOME}
...
This is the full list, for those who really want to deck out their HotKeyz
{!} !
{#} #
{+} +
{^} ^
{{} {
{}} }
{SPACE} SPACE
{ENTER} ENTER key on the main keyboard
{ALT} ALT
{BACKSPACE} or {BS} BACKSPACE
{DELETE} or {DEL} DELETE
{UP} Up arrow
{DOWN} Down arrow
{LEFT} Left arrow
{RIGHT} Right arrow
{HOME} HOME
{END} END
{ESCAPE} or {ESC} ESCAPE
{INSERT} or {INS} INS
{PGUP} PGUP
{PGDN} PGDN
{F1} - {F12} Function keys
{TAB} TAB
{PRINTSCREEN} PRINTSCR
{LWIN} Left Windows key
{RWIN} Right Windows key
{NUMLOCK} NUMLOCK
{BREAK} for Ctrl+Break processing
{PAUSE} PAUSE
{CAPSLOCK} CAPSLOCK
{NUMPAD0} - {NUMPAD9} Numpad digits
{NUMPADMULT} Numpad Multiply
{NUMPADADD} Numpad Add
{NUMPADSUB} Numpad Subtract
{NUMPADDIV} Numpad Divide
{NUMPADDOT} Numpad period
{NUMPADENTER} Enter key on the numpad
{APPSKEY} Windows App key
{LALT} Left ALT key
{RALT} Right ALT key
{LCTRL} Left CTRL key
{RCTRL} Right CTRL key
{LSHIFT} Left Shift key
{RSHIFT} Right Shift key
{SLEEP} Computer SLEEP key
So yeah, you can do that now, which is a major plus - but due to some limitations, I haven't gotten it too work within the actual GUI.
As far as fixes go, you can now quit even if HotKeyz is paused. I know that was annoying for me, so I'm betting it was annoying for alot of other people. Also, in rare cases, the program would queue up hotkeys while it was paused, and when it was unpaused, all hell would break loose. That has now been fixed. Additionally, if you forgot to pause, and are working on something outside of Stick Online and you press a hotkey, its not going to bring up SO like it did before and do its jazz. Hotkeys will only work if SO is running. You still must pause it, however, to type outside of SO while SOHK is running.
Finally, I know one thing that was really wanted, especially by Seifer, was full screen support. However, this hotkeys program is all done externally; there is no way for me to mess with the functions of the game. As such, I can't do full screen currently because the resolution adjusts to the resolution of the monitor you are playing it on. Since that occurs, it would take too much work for me to map every single coordinate for the inventory on every single resolution out there (not to mention, I don't have a big monitor). So, until there is a way I can detect where the inventory icon is, and where the inventory itself is, I'll keep trying to see if I can find a way to make it work.
So yeah. Have fun with it. If you find any bugs, feel free to post 'em here, or if you have any suggestions/comments/criticisms, post them here as well. PM me if you want.
(http://t2.gstatic.com/images?q=tbn:XPD-m5mu6qzQaM:http://freshfunnypictures.com/funny-pictures/3937/internet-ticket.jpg)
For you sir, on the house.
*Edit*
A couple problems I've encountered so far. First, W doesn't seem to appear, but it works nontheless, so that's not really an issue. Second, I can't seem to change the delay using the program, only using the .ini file, however even then I see no change occur. One thing if possible I would like to see in the future, would be the ability to add more than just 8 hotkeys. Whether it be added visually as seperate pages, or just give us the ability to add "Hotkey9" and "Equip9" manually to the .ini, either would be nice. (If you actually can do this, please correct me!)
Great stuff though!
The delay should work, I just tested it though. I think I know why it wouldn't be working for you - try a larger number like 500 or something, and you should see a considerable difference. I changed it directly in the program, and it was working for me. If it still isn't working for you, let me know. Just try a large number, and it should work.
The 'w' doesn't show up because of the input box width (it needs to be longer) Though technically is does, if you highlight it. I have to fix the input boxes, so I'll get on that.
Yeah, I'll probably add more hotkeys in the near future. I've waited thus far on that, because I've been trying to allow it so that you could choose how many hotkeys you want.
Awwwww!!!! :(:(:(
I wanted full screen.
Cool.. I just used JitBit Macro recorder for mine.
I'ma try urs later.
Quote from: Seifer on February 24, 2010, 04:01:29 PM
Awwwww!!!! :(:(:(
I wanted full screen.
Ahhh, I know Seifer :(
Its really difficult, but I'm trying!
Theres no reason you should need to have seperate settings for each possible resolution as far as I can see. If you can figure out the current screen resolution, then the items should all be the same percentage of the way down the screen.
Quote from: Meiun on February 24, 2010, 07:08:09 PM
Theres no reason you should need to have seperate settings for each possible resolution as far as I can see. If you can figure out the current screen resolution, then the items should all be the same percentage of the way down the screen.
I guess it depends how he treating the screen. Now i do not know this is for sure (meaning i think im wrong) but game maker probably makes the window bigger and scales the image. So im guessing when this thing tries to click it misses its point because to it all it does is go to an x/y on the window and not from the graphics output its self.
Non the less the easy fix is to let the user set ware the mouse needs to click.
Quote from: Meiun on February 24, 2010, 07:08:09 PM
Theres no reason you should need to have seperate settings for each possible resolution as far as I can see. If you can figure out the current screen resolution, then the items should all be the same percentage of the way down the screen.
That is just the thing. I tested it on my monitor by changing the resolution, and as far as I could tell, there was no set equation for the distance that the icon/inventory moved. They get stretched out, and appear in different places depending on your resolution, and I couldn't find any correlation between how far the things move and the resolution of the game.
Now you could read the screen height and depth and make an accurate assumption ware things might go when they are full screen.
Quote from: ARTgames on February 24, 2010, 07:42:30 PM
Now you could read the screen height and depth and make an accurate assumption ware things might go when they are full screen.
Yeah, I know how to find the screen height and width - however, there is just no accounting for how much the thing is stretched based on resolution. Like I said, I went through multiple resolutions, some very small to some very high, and the difference between positions were just large and unaccountable.
Quote from: Cactuscat222 on February 24, 2010, 07:55:08 PM
Quote from: ARTgames on February 24, 2010, 07:42:30 PM
Now you could read the screen height and depth and make an accurate assumption ware things might go when they are full screen.
Yeah, I know how to find the screen height and width - however, there is just no accounting for how much the thing is stretched based on resolution. Like I said, I went through multiple resolutions, some very small to some very high, and the difference between positions were just large and unaccountable.
well use variables! :D
stick online window height = SoH
stick online window width = SoW
screen height = SH
screen width = SW
click placement for windows x (the x the mouse clicks on your so hot keys) = x
click placement for windows Y (you get the idea) = y
when in full screen use:
Y = SoH / SH * Y + Y
X = SoW / SW * X + XEdit: ok so im not good at that math stuff, fixed it:
Y = Y - (SoH/SH * Y) + Y
X = X - (SoW/SW * X) + X
Or basically see how much it scaled and add that onto the old click x and y.
edit: ok i fixed the typos. i think
No no. When you go into full screen on Stick Online, it adjusts to your current resolution. So if you are running at 1280 x 1024, SO will become 1280 x 1024; if you are running at 800 x 600, then SO will adjust to 800 x 600 full screen, etc etc.
Right now, in non-fullscreen, SO runs at 950 x 600 or something. When you change from that to any other resolution, there is no set way to tell where the icon/inventory will be, because there is no equation. I would have to go through every resolution and add the correct coordinates, which would take forever, and I can't account for all of them.
EDIT: I see what you mean now, I'll try something.
Edit:
Yeah man this is what that's for. When stick online grows or shrinks to anything that math will also finger out ware to scale the mouse to match up. or so i hope (my math suck ok :P)
try my 2ed one out or post ur source code.
Okay, so I figured out the Delay problem Lucy - an error was making it so only Slot1 hotkeys would be affected by the delay. That has now been fixed, and I'll upload that with the next version.
Art, you got me alot closer, but its still not working. This is what I'm working with
SO is 950 x 600. Respectively, the mouse coordinates for the Inventory Icon are (545, 63). As such, the equation appears as:
(545 - (950/$_size[0] * 545) + 545) for X
(63 - (600/$_size[1] * 63) + 63) for Y
Where $_size[0] is the Full Screen Width, and $_size[1] is the Full Screen Height. So, when SO is not full screen, it works fine, just as the hotkeys always have.
However, putting in my resolution of 1280 x 1024, the numbers come out off
(545 - (950/1280 * 545) + 545) = 685.5
(63 - (600/1024 * 63) + 63) = 89.08
From my own investigation though, the numbers should be around 720 - 730, and 190 - 200. As I try other resolutions, the numbers are further off... so I'm not sure what to do.
Well i was wrong. But i would need tools i don't have now to test stuff that might work. Some one here im sure can help.
Quote from: Cactuscat222 on February 24, 2010, 09:15:00 PM
Okay, so I figured out the Delay problem Lucy - an error was making it so only Slot1 hotkeys would be affected by the delay. That has now been fixed, and I'll upload that with the next version.
Art, you got me alot closer, but its still not working. This is what I'm working with
SO is 950 x 600. Respectively, the mouse coordinates for the Inventory Icon are (545, 63). As such, the equation appears as:
(545 - (950/$_size[0] * 545) + 545) for X
(63 - (600/$_size[1] * 63) + 63) for Y
Where $_size[0] is the Full Screen Width, and $_size[1] is the Full Screen Height. So, when SO is not full screen, it works fine, just as the hotkeys always have.
However, putting in my resolution of 1280 x 1024, the numbers come out off
(545 - (950/1280 * 545) + 545) = 685.5
(63 - (600/1024 * 63) + 63) = 89.08
From my own investigation though, the numbers should be around 720 - 730, and 190 - 200. As I try other resolutions, the numbers are further off... so I'm not sure what to do.
Just a quick thought: Try the equation as more of a percentage of the screen size. So you'd look at 545/950 and 63/600. Now apply that percentage to the actual screen size.
can you explain more ling?
Also i fingered out what was wrong with mine. I just found out that stick online maintains aspect ratio when full screen. I assumed it just made it 100% full screen. I need to work that into my math to make it work right. (i hope)
Just released v1.02. As mentioned in the original post, fixes the delay function so that is now properly works. Re-download if you want to make use of this new function.
Full-Screen support is still being worked on...
These are pretty cool, good job!
Quote from: ARTgames on February 24, 2010, 09:46:09 PM
can you explain more ling?
Also i fingered out what was wrong with mine. I just found out that stick online maintains aspect ratio when full screen. I assumed it just made it 100% full screen. I need to work that into my math to make it work right. (i hope)
Sorry, I just made a quick post cuz I was rushed. But your comment changes things anyways so it doesn't matter. So basically what you're saying is that the width of the game screen extends to the size of the monitor, but the height does not? So you just see black bars? What about if the monitor is wide screen? I think the SO game screen is still wider in aspect ratio than a wide screen monitor so it would probably still have black bars (can anyone confirm?)
Anyways, I think my comment about using percentage of game screen size still holds (although it might be slightly altered for the y axis). Basically, if you look at the standard screen width, which is supposedly 950. You take the X coordinate that you want (in the example it was 545). Now take the percentage of the screen width (545/950 = approx 57%). Now you can use that percentage to get the equivilant X coordinate for any screen width. For example, if the screen width is 1024 you'd do: 1024 x 57% = approx. 583.68.
For height, it's probably different since the screen size would encompass the whole monitor, but the actual game window only uses a portion of that (the rest being black bars). For this, I think I would take the game window ratio (950/600 = approx. 1.58). Now you can use that to get the game window height based on the full screen monitor width (If you're monitor resolution width is 1024 the height of the game window at full screen would be approx. 648). Now you can do the same thing you did above with the X axis, take the desired Y coordinate (in the example 63) and divide by the original screen size to get a percentage (63/600 = 10.5%) now multiply that by the new screen height which was calculated earlier (648 x 10.5% = approx. 68.04).
Someone could check my math, but it seems accurate. There's also some assumtions in there about how the screen size works and whether the black area is included or not. And to be sure, the numbers I was using were rounded so there might be some significant rounding errors by the end of the calculations. If you could rig the variables being used to hold more decimal places it would help reduce or eliminate those errors.
I've got a 22' widescreen running at 1680 by 1050 and i get no black bars. The SO screen completly consumes the monitor.
Looks like the SO screen ratio and your monitor ratio are very similar 1.583~ and 1.6.
Oh, well, I guess your monitor resolution is actually shorter than the SO game screen. In otherwords, if you use the same ratio 1.58, instead of having black bars, the game screen would extend taller than your monitor by around 13 pixels. It's a very minor amount, but the result is that there's probably some minor skewing of the pixels in order for it to fit exactly on your screen. Because of that, using my method above may not work exactly right. It may because of how small a difference it would cause, but there's a chance it would throw the numbers off enough to have the button clicks hit the wrong thing.
Meh, I tried.
Quote from: Lingus on March 01, 2010, 07:30:38 PM
Looks like the SO screen ratio and your monitor ratio are very similar 1.583~ and 1.6.
Oh, well, I guess your monitor resolution is actually shorter than the SO game screen. In otherwords, if you use the same ratio 1.58, instead of having black bars, the game screen would extend taller than your monitor by around 13 pixels. It's a very minor amount, but the result is that there's probably some minor skewing of the pixels in order for it to fit exactly on your screen. Because of that, using my method above may not work exactly right. It may because of how small a difference it would cause, but there's a chance it would throw the numbers off enough to have the button clicks hit the wrong thing.
Meh, I tried.
A worthy attempt, and I'll test it all out to see if it works. Still, as you can see, its complicated because of how it adjusts to different resolutions/monitors.
Quote from: Seifer on March 01, 2010, 07:19:36 PM
I've got a 22' widescreen running at 1680 by 1050 and i get no black bars. The SO screen completly consumes the monitor.
look at the left and right side of your screen. there it is on both sides about 5 pixels big.
Ahhh, your right.
sorry i said i was going to help and have not. iv been lazy.
All you need to do is find out that when your scaling the monitor will the height or the width hit the sides of the screen first.
so do this:
screen_width / screen_height = screen_aspect
so_width / so_height = so_aspect
(you know that already)
If screen_aspect > so_aspect {
/* the users screen is wider then stick online's window, so the game will rez the window till its height fits the screen */
so_height = screen_height
so_width = so_height * so_aspect
}
If screen_aspect < so_aspect { /* if the screen is taller than so's*/
so_width = screen_width
so_height = so_width / so_aspect
/*note "so_aspect" is stick online's original aspect ratio. 1.583 something according to lingus*/
}
if screen_aspect = so_aspect {
so_width = screen_width
so_height = screen_height
/*no dir :P */
}
So now you have stick online's new dimensions. Now run that threw my old post.
stick online window NEW (its so_width from above) width = SoW
stick online window NEW (its so_height from above) height = SoH
screen width = SW
screen height = SH
click placement for windows x (the x the mouse clicks on your so hot keys) = x
click placement for windows Y (you get the idea) = y
edit:
X = X - (SoW/SW * X) + X
Y = Y - (SoH/SH * Y) + Y
wrong, im working on it.
now that should work. But i could have left something out.
Well done Art.
But I don't understand your formula at the end. I understand why you're doing (SoW/SW * X). That's so you can figure out where the coordinate is even if the game width is less than the full screen width. But why are you doing X - (that) + X?
Also, I think you have to bring in the original game window width somewhere.
You need to get the ratio of where the X coordinate is on the original window, and then translate that to the full screen game window width. Then bring in the difference between the game window width and the actual screen width (in case they're different).
Let's see if I can do the formula:
fullX = (originalX / originalSoWidth) x fullSoWidth
screenX = (fullX / fullSoWidth) x screenWidth
Something like that... fullSoWidth is what Art calculated in his post which I believe he was calling SoW. I guess I'm just more descriptive with my variable names. Based on this formula, if fullSoWidth = screenWidth then screenX and fullX will end up equal as well, which is as it should be.
Quote from: Lingus on March 02, 2010, 05:01:11 PM
Well done Art.
But I don't understand your formula at the end. I understand why you're doing (SoW/SW * X). That's so you can figure out where the coordinate is even if the game width is less than the full screen width. But why are you doing X - (that) + X?
I would need to rethink about it. I forgot why.
Quote from: Lingus on March 02, 2010, 05:01:11 PM
Also, I think you have to bring in the original game window width somewhere.
well "so_width / so_height = so_aspect" or the so_width/height is its original window height and width of stick online. sorry if that was not clear.
Quote from: Lingus on March 02, 2010, 05:01:11 PM
You need to get the ratio of where the X coordinate is on the original window, and then translate that to the full screen game window width. Then bring in the difference between the game window width and the actual screen width (in case they're different).
Let's see if I can do the formula:
fullX = (originalX / originalSoWidth) x fullSoWidth
screenX = (fullX / fullSoWidth) x screenWidth
Something like that... fullSoWidth is what Art calculated in his post which I believe he was calling SoW. I guess I'm just more descriptive with my variable names. Based on this formula, if fullSoWidth = screenWidth then screenX and fullX will end up equal as well, which is as it should be.
thats what the last part of my post is suppose to cover. not saying i did it right tho. ;D
Just to be clear, I was only referring to the last part of your post. The first part of your post was the "Well done Art." Everything up to the formulas right at the end looks good. So yea.
edit: most of this is not right. my bad
Ok, crap! Your 100% right about the end. I have no idea what i was thinking on that last part. >_<
edit 3-3-2010
Ok, crap! Your 100% right about the end. I have no idea what i was thinking on that last part. >_< (agen! i keep getting it wrong)
Variables meanings:
click placement for windows x (the x the mouse clicks on your so hot keys in window mode) = x
click placement for windows Y (you get the idea) = y
width in pixels of user native screen rez he running his display at = screen_width
screen_height ( self explanatory )
start out as stick online's original window width, then we change it later = so_width
so_height ( self explanatory )
this will tell you the x of ware your mouse needs to click on the screen when in full screen = ware_to_click_x
ware_to_click_y ( self explanatory )
Script in pseudo code:
screen_width / screen_height = screen_aspect
so_width / so_height = so_aspect
if screen_aspect > so_aspect {
/* The users screen is wider then stick online's window, so the game will rez the window till its height fits the screen */
so_height = screen_height
so_width = so_height * so_aspect
}
if screen_aspect < so_aspect {
/* if the screen is taller than so's*/
so_width = screen_width
so_height = so_width / so_aspect
/* Note: "so_aspect" is stick online's original aspect ratio. 1.583 something according to lingus. */
}
if screen_aspect = so_aspect {
so_width = screen_width
so_height = screen_height
/*simple eh */
}
/*(I took this part from lings post. He gets credit for it.)*/
ware_to_click_x = so_width / 950 * x
ware_to_click_y = so_height / 600 * y
Now its right. ( I hope ) Or really close.
Not quite right yet (at least I don't think)
Take a look at my formula again:
QuotefullX = (originalX / originalSoWidth) x fullSoWidth
screenX = (fullX / fullSoWidth) x screenWidth
Notice, this is only for X. You need these 2 formulas to get the final placement of each coordinate.
I think what you're doing in your if statements, you're replacing a variable you will need later. So instead of doing this:
Quoteso_width = screen_width
It should be:
Quotefull_so_width = screen_width
Then you can keep that "so_width" for later use.
Here, I rewrote the pseudocode:
QuotescreenWidth / screenHeight = screenAspect
originalSoWidth / originalSoHeight = soAspect
if screenAspect > soAspect {
/* The users screen is wider then stick online's window, so the game will rez the window till its height fits the screen */
fullSoHeight = screenHeight
fullSoWidth = originalSoHeight * soAspect
}
if screenAspect < soAspect {
/* if the screen is taller than so's*/
fullSoWidth = screenWidth
fullSoHeight = originalSoWidth / soAspect
/* Note: "so_aspect" is stick online's original aspect ratio. 1.583 something according to lingus. */
}
if screenAspect = soAspect {
fullSoWidth = screenWidth
fullSoHeight = screenHeight
/*simple eh */
}
fullX = (originalX / originalSoWidth) x fullSoWidth
screenX = (fullX / fullSoWidth) x screenWidth
fullY = (originalY / originalSoHeight) x fullSoHeight
screenY = (fullY / fullSoHeight) x screenHeight
Also, wrapped around the whole thing, you need to check if the actual game window screen size is larger than the established original size. So something like:
Quoteif currentSoWidth > originalSoWidth {
[code from above]
}
Haha, wow guys, thanks for doing this -.- I haven't had the time to try it yet, but I will shortly. I was working earlier on it, but you guys got farther than I did. I'll update soon too let you know if this works.
No problem. I have fun doing stuff like this. Having a problem and trying to figure it out with other people. Good stuff.
Ok i know i have done something wrong. My next post is not going out without me testing it.
Quote
Also, wrapped around the whole thing, you need to check if the actual game window screen size is larger than the established original size. So something like:
Quoteif currentSoWidth > originalSoWidth {
[code from above]
}
what? whats the "established original size"?
ok i think all i really need to do is change this
so after my if's change:
ware_to_click_x = screen_width / so_width * x
ware_to_click_y = screen_height / so_height * yto
ware_to_click_x = so_width / so_width_original * x
ware_to_click_y = so_height / so_height_original * y
so by "so_width_original" i mean stick onlines original window size. it does not even need to be a variable. it could just be a constant.
this would be better.
ware_to_click_x = so_width / 950 * x (do not forget x is the old place to click when so is in window mode)
ware_to_click_y = so_height / 600 * y
I forgot what i needed to do is compare so old size to the new one and your post told me that. ty ling. that was my bad!
i edit my post at top to reflect what i said in this post.
http://www.stick-online.com/boards/index.php?topic=786.msg21049#msg21049
Quote from: ARTgames on March 03, 2010, 05:08:32 PM
Quote
Also, wrapped around the whole thing, you need to check if the actual game window screen size is larger than the established original size. So something like:
Quoteif currentSoWidth > originalSoWidth {
[code from above]
}
what? whats the "established original size"?
That's the 950x600. So if the game window size is 950x600, you don't want the code to do anything. If it does, then it will think the game size is the full screen size.
Quote from: ARTgames on March 03, 2010, 05:08:32 PM
ok i think all i really need to do is change this
so after my if's change:
ware_to_click_x = screen_width / so_width * x
ware_to_click_y = screen_height / so_height * y
to
ware_to_click_x = so_width / so_width_original * x
ware_to_click_y = so_height / so_height_original * y
so by "so_width_original" i mean stick onlines original window size. it does not even need to be a variable. it could just be a constant.
this would be better.
ware_to_click_x = so_width / 950 * x (do not forget x is the old place to click when so is in window mode)
ware_to_click_y = so_height / 600 * y
I forgot what i needed to do is compare so old size to the new one and your post told me that. ty ling. that was my bad!
i edit my post at top to reflect what i said in this post.
http://www.stick-online.com/boards/index.php?topic=786.msg21049#msg21049
I still think that's not quite right. Because there's a difference between what you're getting as the full screen game window size and the actual game window size. When you're in full screen, I assume the game window size is actually the entire screen, but where the game actually displays is smaller (hence the black bars). But the black bar area is still actually part of the game window.
As an example, if you take 1280x1024 monitor resolution. You use your formula to calculate the full screen game window size:
(Also, note the variable in red is where I found a mistake in the code from my previous post.)
QuotescreenWidth(1280) / screenHeight(1024) = screenAspect(1.25)
originalSoWidth(950) / originalSoHeight(600) = soAspect(1.58)
if screenAspect(1.25) < soAspect(1.58) {
fullSoWidth(1280) = screenWidth(1280)
fullSoHeight(810) = screenWidth(1280) / soAspect(1.58)
}
So you have a game screen size of 1280x810 which is the same aspect ratio as the original game window size. What that does not account for is that the actual game window size is really 1280x1024, but a portion of that 1024 is black bar. That's where my two formulas are coming into play. It finds the coordinates if the game size were 1280x810, and then it finds the real coordinates based on the full screen size of 1280x1024.
I see what your saying now. See i was trying to do that but i still did make a mistake.
so_width = screen_width
so_height = so_width / so_aspect
that is really worng! >_<
edit:
cac read Lingus post! he got it!
edit:
Lingus is that what your telling me?
stick online width (1680) = screen width (1680)
stick onlines new height (1061~) = stick online original height (600) * stick online new width (1680) / stick online old width (950)
see i thought all i had to do was divide one number to solve the black bars. man i was not thinking!
Err... not sure. I'll have to look at this post again later (I'm half out the door).
I think i got my math up there wrong also. >_<.....
This is the basic concept i was trying to do.
http://img10.imageshack.us/img10/2329/mathnp.jpg
Now i know for sure this is right! Lingus if you say that's wrong I'm giving up. This math is NOT for me. :P
Art, I always took you for a fool since you can't write. But it turns out your actually quite the bright lad. So I just wanted to say Oh Hai, congrats on being way better than I thought you were. <3
But it's looking good. That math makes sense. I hope it works.
Quote from: Seifer on March 03, 2010, 11:04:04 PM
Art, I always took you for a fool since you can't write.
yeah i agree. that happens a lot. i wish i was a better writer.
Quote from: Seifer on March 03, 2010, 11:04:04 PM
But it's looking good. That math makes sense. I hope it works.
I don't agree really. Its taken me a lot of post and i mess up alot. Its not that i have intelligences, its that i like stuff that other people don't really care about. If more people cared about math i would be most likely below normal. But hey im doing it for fun.
Quote from: ARTgames on March 03, 2010, 10:07:40 PM
I think i got my math up there wrong also. >_<.....
This is the basic concept i was trying to do.
http://img10.imageshack.us/img10/2329/mathnp.jpg
Now i know for sure this is right! Lingus if you say that's wrong I'm giving up. This math is NOT for me. :P
Okay yea that part looks right, but did you understand what I was saying about the black bar area actually being part of the game screen? This is something that I may have wrong because I don't know GM very well and/or I would have to actually test it using an AutoIt screen reader or something to see what the actual window size is when it's full screen. My thinking is that if the monitor resolution is 1680x1050, that the game window when full screen will really be 1680x1050, not 1662.5x1050 as in your calculations. In other words, the black bar area is included in the real game window size.
Even so, you still need your calculation to determine where the new coordinate will be when scaled up. Then you have to find where the coordinate will be when including the black bars (because that's the REAL coordinate within the game window if the game window includes the black bars). That's why I have two different formulas to find each coordinate.
good point! man I'm dumb. well we know its going to center it. so lets try:
if screen_aspect < so_aspect {
/* if the screen is taller than so's*/
....
stick_online_new_screen_draw_width = x (x of ware the game starts drawing now its window)
screen_height / 2 - stick_online_new_screen_draw_height / 2 = y
}
Use this x,y and add your offset for the new clicking spot.
Quote from: ARTgames on March 04, 2010, 08:26:42 PM
good point! man I'm dumb. well we know its going to center it. so lets try:
if screen_aspect < so_aspect {
/* if the screen is taller than so's*/
....
stick_online_new_screen_draw_width = x (x of ware the game starts drawing now its window)
screen_height / 2 - stick_online_new_screen_draw_height / 2 = y
}
Use this x,y and add your offset for the new clicking spot.
Gm has a bad scaling and fullscreen support (just to add to the list... sadly...)
Your window size in gm becomes same as your resolution... I proved this by:
1. Making an object that draws mouse_x and mouse_y vars on the screen
2. Fullscreenin the game, and dragging the mouse... The maximum x was 640x480... But in reality, that's gm's poor mouse winapi handling...
3. I looked closely, and moved a mouse one pixel away... the coordinates didn't change at all. If it changed your resolution, the mouse coordinates would update.
As simple as that.
Also art, stick_online_new_screen_draw_width is a bad script naming habit >_>...
Quote from: krele on March 05, 2010, 12:24:04 PM
Gm has a bad scaling and fullscreen support (just to add to the list... sadly...)
It used nearest neighbor. Its cheap to compute but as you see is quite ugly.
Quote from: krele on March 05, 2010, 12:24:04 PM
Your window size in gm becomes same as your resolution... I proved this by:
Well that's not in dispute at all. I did over look it while Lingus was trying to make me see it for like 5 posts. :P
Quote from: krele on March 05, 2010, 12:24:04 PM
Also art, stick_online_new_screen_draw_width is a bad script naming habit >_>...
Well i don't name things like that in real scripting silly. Its just super specific so the reader know what I'm talking about.
I will try and put all this info into one simple post with all of Lingus good fixes.
Quote from: ARTgames on March 05, 2010, 05:26:19 PMQuote from: krele on March 05, 2010, 12:24:04 PM
Also art, stick_online_new_screen_draw_width is a bad script naming habit >_>...
Well i don't name things like that in real scripting silly. Its just super specific so the reader know what I'm talking about.
I will try and put all this info into one simple post with all of Lingus good fixes.
Actually, I have received pretty good advice not to abbreviate your variable names. The more descriptive you can be the better. If you start doing things like "SOScnDrwWdth" or whatever then there's no way you're going to remember exactly how you spelled it the next time you need to use that variable. In addition, you might forget what the abbreviation even means.
Quote from: Lingus on March 05, 2010, 07:11:43 PM
Quote from: ARTgames on March 05, 2010, 05:26:19 PMQuote from: krele on March 05, 2010, 12:24:04 PM
Also art, stick_online_new_screen_draw_width is a bad script naming habit >_>...
Well i don't name things like that in real scripting silly. Its just super specific so the reader know what I'm talking about.
I will try and put all this info into one simple post with all of Lingus good fixes.
Actually, I have received pretty good advice not to abbreviate your variable names. The more descriptive you can be the better. If you start doing things like "SOScnDrwWdth" or whatever then there's no way you're going to remember exactly how you spelled it the next time you need to use that variable. In addition, you might forget what the abbreviation even means.
yeah but "stick_online_new_screen_draw_width" is a bit too long. It takes a really long width and takes a while to type. there's a middle ground.
I'm not sure if this is possible, but if you were to implement a way for the mouse wheel to swap through your hotkeys, that would be amazing. Meaning, if you scroll up with the mouse wheel it goes from hotkey 1 to hotkey 2, or scroll down from hotkey 1 to hotkey 8, etc. I don't know if theres any way for it to remember the last hotkey it used, /shrug.
Quote from: ARTgames on March 05, 2010, 07:42:14 PM
yeah but "stick_online_new_screen_draw_width" is a bit too long. It takes a really long width and takes a while to type. there's a middle ground.
I would point out that none of the variable names I came up with were that long, yet they were still descriptive and did not use abbreviations. Just saying.
Quote from: Lucifer on March 10, 2010, 08:54:38 PM
I'm not sure if this is possible, but if you were to implement a way for the mouse wheel to swap through your hotkeys, that would be amazing. Meaning, if you scroll up with the mouse wheel it goes from hotkey 1 to hotkey 2, or scroll down from hotkey 1 to hotkey 8, etc. I don't know if theres any way for it to remember the last hotkey it used, /shrug.
The major issue I would see with that is that the mouse wheel scroll is too fast. Because of how this kind of macro functions, it needs time in between hotkey presses. It could go one of two ways. It would either ignore your input while it is attempting to switch items and so any wheel scrolls during that time would not do anything until the macro is finished (you could probably also make sure in the code that this happens) or it would attempt to do multiple macros at a time therefore screwing up everything. I know the macro tools I was using in the past were kind of unreliable in that sense. If someone pressed keys too quickly it had the potential of messing something up.
I'm curious what is being used on this program? Something like AutoIt?
Quote from: Lingus on March 10, 2010, 09:10:39 PM
Quote from: ARTgames on March 05, 2010, 07:42:14 PM
yeah but "stick_online_new_screen_draw_width" is a bit too long. It takes a really long width and takes a while to type. there's a middle ground.
I would point out that none of the variable names I came up with were that long, yet they were still descriptive and did not use abbreviations. Just saying.
I know i know. I was just wanted to say something back to you.
Aye Lingus, I programmed this with AutoIt.
Sorry I haven't gotten around to trying out your guys ideas on Full screen, I'll do that soon, I promise.
@Luci: Yeah, I could definitely try something like that in the near future. Shouldn't be too hard. My program responds pretty well to quick pressing of the keys, in the sense that it doesn't queue the actions, and it doesn't interrupt itself... though I haven't tried in awhile.
So I took the time to do it right and I checked my work.
This will help you get full screen working.
screen_width = <screen horizontal resolution here>
screen_hight = <screen vertical resolution here>
window_width = <window horizontal resolution here>
window_hight = <window vertical resolution here>
mouse_pos_click_x = <the x position you click in window>
mouse_pos_click_y = <the y position you click in window>
screen_aspect = screen_width / screen_hight
window_aspect = window_width / window_hight
mousex_aspect = mouse_pos_click_x / window_width
mousey_aspect = mouse_pos_click_y / window_hight
if ( screen_aspect > window_aspect) // If your screen is more wide than the window.
{
new_window_width = screen_hight * window_aspect
new_window_hight = screen_hight
mouse_click_new_x = new_window_width * mousex_aspect + ( screen_width - new_window_width ) / 2
mouse_click_new_y = new_window_hight * mousey_aspect
}
else
{
window_aspect = window_hight / window_width
new_window_width = screen_width
new_window_hight = screen_width * window_aspect
mouse_click_new_x = new_window_width * mousex_aspect
mouse_click_new_y = new_window_hight * mousey_aspect + ( screen_hight - new_window_hight ) / 2
}
"mouse_click_new_x" and "mouse_click_new_y" are your new coordinates to click when in full screen. Make full screen happen now!
Yes please, I need this so i don't have to change my resolutions when i sit back with an Xbox controller. (And more slots wouldn't hurt. :x)
Yes! What turkey just said x 1,000,000. I used to play this all the time with a Gamepad, while watching tv shows or whatever on my second monitor, since this is mostly mindless. Since I was also watching TV, I'd lay in bed and play full screen, except I couldn't use the damn hotkeys to change around gear from afar!
I'll get right to work.
Why Hello, here's an idea for SO V3.
The Game could check if the player has the process of the hkey-tool running and show it visually ingame.
e.g. if any player starts the tool (or disable the pause function if already started) a few pixels of his right arm (can be anything else, this is just an example) will be coloured red.
This will save GMs in tournaments the job to find out if anyone has hkeys enabled or not.
I didn't post this in suggestions, since I thought this topic would fit better.
Quote from: CherryPie on November 03, 2010, 04:52:50 PM
Why Hello, here's an idea for SO V3.
The Game could check if the player has the process of the hkey-tool running and show it visually ingame.
e.g. if any player starts the tool (or disable the pause function if already started) a few pixels of his right arm (can be anything else, this is just an example) will be coloured red.
This will save GMs in tournaments the job to find out if anyone has hkeys enabled or not.
I didn't post this in suggestions, since I thought this topic would fit better.
He could probably still do it in this version..
Quote from: igufed on November 03, 2010, 04:58:12 PM
Quote from: CherryPie on November 03, 2010, 04:52:50 PM
Why Hello, here's an idea for SO V3.
The Game could check if the player has the process of the hkey-tool running and show it visually ingame.
e.g. if any player starts the tool (or disable the pause function if already started) a few pixels of his right arm (can be anything else, this is just an example) will be coloured red.
This will save GMs in tournaments the job to find out if anyone has hkeys enabled or not.
I didn't post this in suggestions, since I thought this topic would fit better.
He could probably still do it in this version..
He can. SO already checks to see if Cheat Engine/other hack tools have processes running. Although I don't know how much editing would be required to detect the hotkeys as I've never used program detection.
I know that its already possible, but Meiun said that there will be no major feature change in V2 besides the clan update.
Therefore I targeted V3.
Guesssss what.
Full screen support is now added and should be working just fine~! Thanks so much ARTGames and Lingus!
Just download from the same link, remove your old version (You can keep your old HKSettings.ini, that should still be compatible), place down your new one, and you should be all set.
If you find any resolutions that don't work or bugs with the full screen, please let me know asap, and I'll get right on fixing it!
Thanks and enjoy!
how come it doesn't switch right away when I like press the button sometimes I haft to like press it twice? But ya it works ALOT better now thank you! :D
thanks, sitting away more than 1m from my screen most of the time so fullscreen support is very useful :)
I have to exit out of hotkeyz to press esc -_- thats kind of annoying..
Quote from: darkflash on May 02, 2011, 08:43:33 AM
I have to exit out of hotkeyz to press esc -_- thats kind of annoying..
I find it alot more helpful than annoying, it helps so i don't accidentally quit the game.
And also, if your going to log out of stickonline you are probably going to close your hotkeys too, so get over it.
YAY FULLSCREEN
Quote from: Cactuscat222 on May 02, 2011, 06:33:24 AM
Thanks so much ARTGames and Lingus!
Your welcome!
What did I do?
Edit: Oh, I guess I helped to come up with some of the math for the fullscreen version... around a year ago! Damn Cactus, what took so long?
Lol, jk. Good work keeping this hotkey program going. I remember when I had one way back in the day. I kept it pretty much to a few select people (it was before there was a precendent for using hotkeys so I wasn't sure if Meiun would be happy about it). But even then it was a task to keep it working for everyone.
It took so long because I'm lazy. :P (And because it was my senior year of highschool)
But what matters is it is here now, and should be working. So thanks for the math anyhow!
The link is broken :O
Please fix it :)
Sorry about that, if you want to download it, try igufed's site - http://v2info.stick-league.com/
Quote from: Cactuscat222 on November 29, 2011, 01:35:55 AM
Sorry about that, if you want to download it, try igufed's site - http://v2info.stick-league.com/
Yeah i found i about 2 hours after i posted this when i tried searching for it in google... god im lazy :P