easyaspi314

There appears to be two bugs, one is a bug where textures are a mess if you turn when up close to a wall (integer overflow/divide by zero, perhaps?) This...

Found it, thanks.

OK so I think the code is `Display.getRealSize();`. I found a solution that _may_ work using reflection on 4.0-4.1 and the current method on 4.2+. I will test it this...

I also heard that **KitKat blocked overlays on the navbar completely** because it could be a DDoS. So that might be why we are getting the weird patterns on some...

@pelya can you explain what exactly you are doing here? ``` java Point displaySize = new Point(); windowManager.getDefaultDisplay().getRealSize(displaySize); Point windowSize = new Point(); windowManager.getDefaultDisplay().getSize(windowSize); displaySize.x += displaySize.x - windowSize.x; displaySize.y...

Just got these ghost touches on my LG G3 on 50%. Here is a screen capture on that setting. Sorry about the quality, but I'd rather not upload a 50MB...

I know. I just wanted to show that. It also happens when viewing a screenshot of it in the Gallery, so it might be out of our control.

Well since I took a screenshot and it glitched out in the Gallery, it looks like it is hardware. On Feb 20, 2017 5:11 AM, "Sergii Pylypenko" wrote: > I'm...

Haven't done the flags yet, but this is a start. ```cpp case UD_Iror: { auto size = operand(0).size(); if (hasOperand(1)) { _[operand(0) ^= (unsigned_(operand(0)) >> operand(1)) | (unsigned_(operand(0)) > constant(1))...

I also removed the GetCurrentProcess hack, removing a dependency on a deprecated ApplicationServices API. Everything *seems* to work, but I don't exactly understand the problem it is trying to solve.