Forum Replies Created
-
Posts
-
I have several ideas for that, i wanted make it in the past, but i was lazy. I can return there when i get out of the pile made from storage restrictions mess.
I think no, I don’t remember work on something like this. The only way is implementation. Some deadly strike actions are cross thread and toast must be fired on main thread, but it should not be big problem.
Why do you need it?
Thank I will debug it today/tomorrow.
If is app in the background then may be killed by system, whenever system makes this decision. In developer options is possibility to increase count of processes in the background.
But that menu acting is weird, i will check it.
Hm and about which problem we are talking? From screenshots i though the problem is that cursor is not in middle of screen after mouse reset. Because you wrote, “you can see the target and where it actually ends up.” If is not in middle after reset then it breaks absolute mouse.
Just now I notice that svn core correctly set cursor position, normal core does it a bit off. I must check why is there difference, maybe bug.
If the cursor is in middle after mouse reset and emulated program does not manipulate with cursor position then it should work.
Star commander seems works fine with enabled svn core, at least after in minutes of testing
Alex, scaling cannot affect pixel traps. Pixel traps detect bytes in original buffer from dosbox. Stretching is done on gpu.
Only if you change game resolution then it is affected
Yeah, I know, while layers and pixel trap automation are cool features, designing it on small screen is pain. And I dont know how to improve it significantly, small screen is small screen, designing for desktop gives more place.
>unfortunately that Target issue is a huge pain, it never seems to work the same way twice, in a deadly strike action.
Hm, I can check it, this sounds weird. Did you tried it in other games? Maybe it is game specific issue. I will try to find the time for testing it tomorrow.
Hi,
This is implemented. You can place one widget over another. Set the top most widget to non blocking. This lets bubble the touch event to widget below. One deadly strike can execute another deadly strike.
In addition, there is pixel trigger what can trigger widget on specific pixel. But the solution above is probably what you need.
No, it should have nothing todo with tablet. Did you went through installation process or you try run some installed version?
I am working on fix, in next days it could be done. Then I can share you fixed version for testing. I can ping you with email.
On android 12 (at least on pixel 3 phone) I have problem with broken layouts. It always worked, since 2014. Google made a bug or change, I must fix it. I have samsung s6 tab light, maybe I will get a12 update soon and can check it. Maybe it is only broken on pixel phones. These phones are really abandoned.
