GithubHelp home page GithubHelp logo

Comments (11)

univrsal avatar univrsal commented on August 23, 2024

Looks like a value is wrapping around. Each element that is wider than one gets a x-offset, like the spacebar here (You can see that it is offset a little to the right):

image
Somehow this value is 32758, which obviously moves the element offscreen.

from input-overlay.

univrsal avatar univrsal commented on August 23, 2024

Ok, so this offset calculation does not work, with the negative base offset in key_space_h.
It works now, there'll be a release for 4.7.3 (Edit it's up) later. Also: You might want to fix the cropping on your texture it looks quite a bit off.
image

from input-overlay.

GreenyNeko avatar GreenyNeko commented on August 23, 2024

Okay using the newest version it now looks like this:

image

Shouldn't the offset between shift and space be equal to the offset between the other keys?

About the cropping.. each of my keys is 157x128 as defined in the .ini with a 1px border and 1px space between each key. The shift key is 334x128 (2 * 157) and the space key is 491x128 (3 * 157).

I used the wasd-minimal as the base for this.

from input-overlay.

univrsal avatar univrsal commented on August 23, 2024

You need a 1 pixel border around the entire texture and a 3 pixel gap in between each key.
Try doing that and then give me the texture again so I can take a look the spacing for space and shift.
Try uploading the actual .png so I get the transparency

from input-overlay.

GreenyNeko avatar GreenyNeko commented on August 23, 2024

keys

from input-overlay.

univrsal avatar univrsal commented on August 23, 2024

Okay, I guess there's still something wrong with the calculation.
With buttons that span over multiple columns, you'll have to take into account that the offset is -20.
So shift for example would have to be 294 (=2 * 157 - (1 * (-20)) and space would have to be 431 (=3 * 157 - (2 * (-20)).
So a key which has the width of n columns would have this formula n * 157 - ((n - 1) * (-20)) for its width.
Anyways I fixed the calculations and it works now (Don't mind the additional shift key):
image
Here's the texture I used (The gaps are still a little off, but I'll leave that up to you)
Install v4.7.4 and see if it works for you

from input-overlay.

GreenyNeko avatar GreenyNeko commented on August 23, 2024

Finally, now it should be fine from the positioning in the .png file. Now, I've tested v4.7.4 and it's not working like it does for you, did you change the .ini file?

image

image

Result without debugging:
image

Transparency file:
keys

from input-overlay.

univrsal avatar univrsal commented on August 23, 2024

Did you read what I wrote? You need to adjust the width of the space and shift key to account for -20 pixel space in between buttons. I even attached a texture file with the correct width, try and use it and see if it works

from input-overlay.

GreenyNeko avatar GreenyNeko commented on August 23, 2024

Ah, sorry. I see.

That's kinda inconvenient/complicated/not intuitive.. You don't take the -20 pixels into account on 1x1 keys. (file says they're 157x128 and they're 157x128 in the wasd-minimalist and in my file).
So why do you have to take it into account on longer ones in the graphics file?
If one is 2 times as long it should be 314x128 in the file. The space which is supposed to be 3 times as long should be 471x128.

When I change the offset on 1x1 keys I don't have to edit the .png file.
When I change the offset and have keys with a multiplier I need to edit the .png file and correct it to take the new offset into consideration?

from input-overlay.

univrsal avatar univrsal commented on August 23, 2024

If you don't take the gap into account, your shift and space keys will take up more space than the 1x1 keys:

docewa

Does it make sense now?

Also, I know that this isn't user friendly, hence why I've spend the last few months coming up with something better for 5.0

from input-overlay.

GreenyNeko avatar GreenyNeko commented on August 23, 2024

Ah, then good luck to you sir and thanks for the good support!

I'll be waiting in the shadows until I notice something else.

from input-overlay.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.