| Summary: | Changing orientation on the devices throws off touch scaling | ||
|---|---|---|---|
| Product: | SDL | Reporter: | vctos <vctos> |
| Component: | *don't know* | Assignee: | Ryan C. Gordon <icculus> |
| Status: | RESOLVED INVALID | QA Contact: | Sam Lantinga <slouken> |
| Severity: | normal | ||
| Priority: | P2 | CC: | gabomdq |
| Version: | HG 2.0 | ||
| Hardware: | All | ||
| OS: | Android (All) | ||
| Bug Depends on: | 1506 | ||
| Bug Blocks: | |||
|
Description
vctos
2012-09-20 07:11:29 UTC
I'm having problems understanding why you opened this report, what's the problem you are seeing? Currently Android does the exact same thing the iOS backend does, so I guess I don't understand what you mean by "this produce incompatibles with other platforms." IMHO, struct SDL_Touch oriented not only for android & ios, it has members "for future use" (for use with tablet digitizer like device). puppose such data sets is to produce coordinate convertion from device (tablet digitizer) coordinat system into (video) screen coordinat system. in current implementation when x_min always 0 and x_max always 1.0, native_xres member redundant. I hope Sam Lantinga can say us exactly, what he mean in SDL_Touch field list. The SDL_Touch structure is made to be as generic as possible, if you look at what information digitizers provider, you'll see it's very similar to what SDL_Touch stores. If you have further doubts you can clear them up in the mailing list. |