Mouseover cursor isnt the same as non mouseover anymore

[makedir]

Please give option to change this, it is really annoying to have a different cursor when mouse over, really bad design decision. I just want to change the color not the complete cursor, especially not into a circle one.

[PandaTeemo]

youd need to take the original game mouse cursor and modify it yourself and
add it as a custom cursor to YM. its too tricky to automatically change
existing game cursors to some new color.

otherwise im not entirely sure what youre asking :)

On Sun, Jan 24, 2016 at 5:38 AM, makedir notifications@github.com wrote:

Please give option to change this, it is really annoying to have a
different cursor when mouse over, really bad design decision I just want to
change the color not the complete cursor, especially not into a circle one

—
Reply to this email directly or view it on GitHub
#3.

[makedir]

No... you did not understand. Since I updated to 0.6.1beta you changed the mouseover cursor to always being the round annoying way too big circle. Before 0.6.1 the default behavior was pink/blue: http://i.imgur.com/jqNOQmK.png => http://i.imgur.com/g9MUxBq.png or vice versa, switching the color when mouseover. Now it switches from: http://i.imgur.com/g9MUxBq.png to http://i.imgur.com/ODGdYmI.png . Please give an option to change this behavior back.

[PandaTeemo]

oh that, the new behavior is hitting "ctrl alt shift 1" repeatedly cycles
through 10 different arrow cursors, "ctrl alt shift 2" cycles through the
circles, etc. this was a necessary change to handle way more cursors.

On Mon, Jan 25, 2016 at 3:48 AM, makedir notifications@github.com wrote:

No... you did not understand. Since I updated to 0.6.1beta you changed the
mouseover cursor to always being the round annoying way too big circle.
Before 0.6.1 the default behavior was pink/blue:
http://i.imgur.com/jqNOQmK.png => http://i.imgur.com/g9MUxBq.png or vice
versa, switching the color when mouseover. Now it switches from:
http://i.imgur.com/g9MUxBq.png to http://i.imgur.com/ODGdYmI.png . Please
give an option to change this behavior back.

—
Reply to this email directly or view it on GitHub
#3 (comment).

[makedir]

What? No... O_0 you still didnt get it. IT IS ALWAYS A CIRCLE WHEN MOUSEOVER, this is terrible. Please change it back or give option to change it. It wasnt before 0.6.1. that way. I want the cursor to change colors not change always into a circle. The damn circle also is always the size too big size, regardless of the non mouseover cursor...

[PandaTeemo]

yes, just use CTRL ALT SHIFT 1 multiple times for all different arrow
cursors.... 2 is for circles 3 is for cross

you may have to change existing cursors when upgrading, including mouseover.

it has to be this way to handle many cursors, you can still download old
version.

On Mon, Jan 25, 2016 at 3:23 PM, makedir notifications@github.com wrote:

What? No... O_0 you still didnt get it. IT IS ALWAYS A CIRCLE WHEN
MOUSEOVER, this is terrible. Please change it back or give option to change
it. It wasnt before 0.6.1. that way. I want the cursor to change colors not
change always into a circle.

—
Reply to this email directly or view it on GitHub
#3 (comment).

[makedir]

DUDE. Are you serious?? How many times shall I tell you, how many times to do you need to understand this problem?

CTRL ALT SHIFT 1 CHANGES THE NON-MOUSEOVER http://i.imgur.com/jqNOQmK.png CURSOR
CTRL ALT SHIFT 2 CHANGES THE NON-MOUSEOVER circle cursor

I AM USING CURSOR 1 FOR NON-MOUSEOVER: CTRL ALT SHIFT 1

PROBLEM/BUG: IT IS ALWAYS CURSOR 2 FOR MOUSEOVER, THIS IS A BUG AND NOT WANTED BEHAVIOR.

Dont you understand, do I need to record a video with my phone dammit??

Problem 1: regardless of the CTRL ALT SHIFT 1-0, the mouseover IS ALWAYS THE PINK CIRCLE
Problem 2: pink mouseover cursor IS ALWAYS THE SAME SIZE

[makedir]

Respond please? Did you understand now the two issues?

[PandaTeemo]

here was reply....

---

theres no concept of mouseover in YM. its just whatever cursor you see you
change with hotkey.

maybe you should specify the game youre talking about. some games, like d3,
change the mouseover cursor to something else while you hold down SHIFT or
ALT preventing YM from changing the intended cursor.

On Tue, Feb 2, 2016 at 8:45 AM, makedir notifications@github.com wrote:

Respond please? Did you understand now the two issues?

—
Reply to this email directly or view it on GitHub
#3 (comment).

[makedir]

https://dl.dropboxusercontent.com/u/14937594/yolo.mp4

[PandaTeemo]

if you cant reassign that mouseover cursor (using YM hotkeys) i think itd
easiest for you to just delete the ...diablo3... file in

C:\Users...\AppData\Local\YoloMouse\

then restart yolomouse and d3. this will clear all assigned cursors and let
you reassign everything.

On Wed, Feb 3, 2016 at 5:01 PM, makedir notifications@github.com wrote:

https://dl.dropboxusercontent.com/u/14937594/yolo.mp4

—
Reply to this email directly or view it on GitHub
#3 (comment).

[makedir]

How do I deactivate all hotkeys, it seems there is no option for this in the ini file.

[PandaTeemo]

if hotkeys dont change mouseover cursor then its a bug. but its working for
everyone else so its probably specific to your setup. clearing old settings
and redoing it should clear it as stated in last email.

On Wed, Feb 3, 2016 at 5:47 PM, makedir notifications@github.com wrote:

Could you for a moment please stop being so ignorant, I know it is hard as
a developer and maker of a program, I tend to do it myself and listen to me
maybe for one second.

THIS IS A DAMN BUG, no TWO:

Why dont you understand this problem? Look at the damn video.

regardless of the assigned MAIN cursor, whenever you mouseover over a
monster in Diablo 3, YoloMouse changes the cursor to a CIRCLE, ALWAYS A
CIRCLE.
2.

the ALWAYS CIRCLE IS ALWAYS THE SAME SIZE, hotkey size is IGNORED FOR
THE MOUSEOVER CURSOR.

—
Reply to this email directly or view it on GitHub
#3 (comment).

[makedir]

How do I deactivate all hotkeys, it seems there is no option for this in the ini file. There need to be some setting like allhotkeysoff or a toggle key for locking hotkeys.

[PandaTeemo]

theres no point to this, just delete the diablo3 ini file and restart d3/ym

On Thu, Feb 4, 2016 at 6:23 AM, makedir notifications@github.com wrote:

... How do I deactivate all hotkeys, it seems there is no option for this
in the ini file. There need to be some setting like allhotkeysoff.

—
Reply to this email directly or view it on GitHub
#3 (comment).

[makedir]

I am not asking without a reason. If I ask something there is a reason for. Please give an option to disable any hotkeys or give a hotkey to toggle them on/off. The hotkeys both alt + ctrl + shit 0-9 (1-x are mostly diablo keys, shift is force stand, alt gr is my ts key, so it happens a lot those are all pressed together at once) and alt -/+ (sound volume) are in conflict with Diablo 3 and my setup, and I dont want to change them to some nonsense bogus workaround to just let this work. There are 12 hotkeys which doesnt make sense to bind them to workaround bogus values to stop this issue to happen, just give an option to toggle all off or deactivate them, or not bind them at all.

There is no logical reason to have cursor 1-9 to be binded to hotkeys this is bad design. Give option like:

CursorKey2=
...
CursorKey9=

or something to deactivate those.

The problem with those changes you made into yolomouse isnt obvious and the "howto" on the page isnt 100% correct for understanding the new mechanics. Before 0.6.1 there was no change for any mouse cursor, so this problem didnt happen.

[PandaTeemo]

you can just remove hotkey bindings in settings.ini effectively disabling
them

On Thu, Feb 4, 2016 at 2:07 PM, makedir notifications@github.com wrote:

I am not asking without a reason. Could you just answer to my damn
questions, yes. If I ask something there is a reason for. Please give an
option to disable any hotkeys or give a hotkey to toggle them on/off.

—
Reply to this email directly or view it on GitHub
#3 (comment).

[makedir]

So if I change them to

CursorKey2=

it will already work / disable them?

[PandaTeemo]

yes, but theres little reason to do this

On Thu, Feb 4, 2016 at 3:07 PM, makedir notifications@github.com wrote:

So if I change them to

CursorKey2=

it will already work / disable them?

—
Reply to this email directly or view it on GitHub
#3 (comment).

[makedir]

Yes there is big reason to do that. I know from a developers point of view there is "always no reason" or "always a reason" to do something or to not give any options/settings at all. I am a developer myself and I know how hard it is to step away from something you created and look at it from an "users" point of view, or from a objective point of view. I tend to do it myself, sadly most stand-alone developers love their "creation" too much to acknowledge improvements or just simple toggle options to turn stuff on and even more important, off. Developers tend to change something they think is a total improvement where it is not and worse, never give any simple options to turn those changes off or back. There is reason behind good human-machine interaction, and a program can be good "inside" but totally bad outside. There are lots of flaws in yolomouse in this part. There isnt always just black and white, but most developers think that way. And what they think is most important could be totally different for someone else. It is always most important for a good program to let the user decide and not decide for the user what to do. If something can be turned off, give option to do that.

[PandaTeemo]

well im just saying disabling hotkeys doesnt really change anything, but
the option does exist by editing settings.ini. i may make a more friendly
UI for this later though.

hopefully wiping the d3 ini fixed your problem of the stuck circle binding.

On Thu, Feb 4, 2016 at 3:51 PM, makedir notifications@github.com wrote:

Yes there is big reason to do that. I know from a developers point of view
there is "always no reason" or "always a reason" to do something or to not
give any options/settings at all. I am a developer myself and I know how
hard it is to step away from something you created and look at it from a
users point of view, or from a objective point of view. I tend to do it
myself, sadly most stand-alone developers love their "creation" too much to
acknowledge improvements or just simple toggle options to turn stuff on and
even more important, off. Developers tend to change something they think is
a total improvement whre it is not and worse, never give any simple options
to turn those changes off or back.

—
Reply to this email directly or view it on GitHub
#3 (comment).