brunodev85
Add an option to map the cursor directly to touches
This PR adds a new way to control the mouse cursor. When enabled, the cursor will jump directly to the position of a touch input. The left button is pressed while the touch is active, and the cursor can be dragged in this state. The right button can be pressed with a two-finger tap. This makes the experience of playing certain mouse-based games much better.
I went to the github page specifically to see if anyone already had a feature request or something for this - lo and behold there's a PR! can't wait for this to get merged (as in I'll probably be building your repo from source)
Hello,
I've tested this branch, you can improve the following :
- the "Map cursor directly" option should be available in the "input control" fragment
- double click doesn't work in this mode, it's anoying for file browsing
- in the game I tried (Balatro), the click is only registers after the next touch
I think it's still better than original mouse inputs for this kind of game
Btw this project was a mess to build with Gradle.
add fix option fix graphics games for example, in ludo race the graphics are not the same as in the screenshot
and also that games that support 1024x768 run even at other resolutions, for example 800x600, 640x480 and others, because when I run games that require a resolution of 1024x768, with the resolution set to 800x600 and 640x480 the game does not start at all, even if you press the icon
@Hydr8gon I've tested your fixes :
- the click and double click gestures work great now
- the "Map cursor directly" option in the "input control" fragment crashes
- there is a build error with the "preferences" attribute missing in TouchpadView, a build CI action would catch this kind of problems
I don't get that crash on my end. Also that error doesn't make sense, because TouchpadView doesn't use Preferences anymore. Could you try a clean build with a fresh clone?
Virgl rnderr full lagging i don't know why i but get more fps when i use exagear & egw The game is smooth, but ever since Winlator was invented, I have had problems with it with the black screen, even though it works well with my friend, but he has a Snapdragon processor. I hve mil i think this issues virgl in winlator
Virgl rnderr full lagging i don't know why i but get more fps when i use exagear & egw The game is smooth, but ever since Winlator was invented, I have had problems with it with the black screen, even though it works well with my friend, but he has a Snapdragon processor. I hve mil i think this issues virgl in winlator
Try changing the Offscreen Rendring Mode from FBO to Backbuffer.
@ClementCariou someone has a problem with the graphics in the Ludo Race game
@ClementCariou someone has a problem with the graphics in the Ludo Race game
Why you mentioned me ? I'm not a contributor.
@longjunyu2 I have a question whether the games will work normally despite changing the graphics from 640x480 to 1024x768 and higher, because some games such as Dark Vampires Shadow of Dust run at a resolution of 1024x768 and if I change to 640x480 and 800x600, the game window is too small and on a normal computer the image is full screen even though the resolution is higher: 1920x1080 and others
@ClementCariouktoś ma problem z grafiką w grze Ludo Race
Dlaczego o mnie wspomniałeś? Nie jestem współtwórcą.
i don't know Could you please write to the developer to fix this problem?
Ok, @TheBoxGame and @abdulazzem, can you not use this random fucking PR to talk about unrelated issues? @brunodev85 should ban you from this github tbh. It's annoying af behavior, and if it were up to me your accounts would've been banned sitewide just for this.
@brunodev85 I have a question whether the games will work normally despite changing the graphics from 640x480 to 1024x768 and higher, because some games such as Dark Vampires Shadow of Dust run in 1024x768 resolution and if I change to 640x480 and 800x600, the game window is not displayed and the image is too small on a normal computer it is full screen despite the higher resolution: 1920x1080 and others
@TheBoxGame @abdulazzem This is not the place to be asking for help or raising an issue. If you'd like help with your problems then make a post on the Winlator subreddit or somewhere else more appropriate. This is a pull request made by @Hydr8gon to, as the title says, "Add an option to map the cursor directly to touches". The only things you should be commenting in this pull request should be in relation to their contribution. So please do not hijack somebody else's hard work to try and get some help that can be easily gotten elsewhere.
@brunodev85 A bit off topic, but why don't you allow Issues? That is to say, how can users report bugs?
@brunodev85 A bit off topic, but why don't you allow Issues? That is to say, how can users report bugs?
This is an interesting question, you should know that Winlator is a very popular software with many stars. The problems that people encounter during use may come from various reasons, such as wine, box64, turinip, dxvk, etc. If the project has enabled issue, that area will become a really messsssssss.
@brunodev85 A bit off topic, but why don't you allow Issues? That is to say, how can users report bugs?
This is an interesting question, you should know that Winlator is a very popular software with many stars. The problems that people encounter during use may come from various reasons, such as wine, box64, turinip, dxvk, etc. If the project has enabled issue, that area will become a really messsssssss.
k, but the problem stands still... Are you saying I should open a pull request to report bugs? That would not be good...
@4Luke4 1: that's not @brunodev85, so what he says in that regard doesn't matter. 2: no, don't do that, that's stupid. 3: this is also not the place to discuss this topic. This is a PR for a specific feature and not a goddamned off-topic community thread!
I don't get that crash on my end. Also that error doesn't make sense, because TouchpadView doesn't use Preferences anymore. Could you try a clean build with a fresh clone?
@ClementCariou Did you ever end up trying this out?
Yeah, I still have the problem. I did the following :
- Go to "Input Controls"
- Check the "Map cursor directly" option
- The application crash
Maybe there are some differences on the project compared to your PR. I know I had to make my own gradle config file to be able to build and package the application.
I don't want to spend more time to troubleshoot it myself.
By the way, can you tell what you have forced pushed recently ? Is it related to this crash ?
@ClementCariou if you get a logcat of the crash and upload it, I could look into it. The force push was just a rebase for the latest upstream changes.
