Qt Simulator Limitations: Difference between revisions
No edit summary |
(clean-up) |
||
| (3 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
[[Qt Simulator]] is fast and lightweight, but is not the same as an emulator, that means, the real OS of the simulated device is not really running, so it has some limitations. | [[Qt Simulator]] is fast and lightweight, but is not the same as an emulator, that means, the real OS of the simulated device is not really running, so it has some limitations. | ||
| Line 9: | Line 7: | ||
=== Architecture === | === Architecture === | ||
Since the application simulated is running in your computer, and there is no hardware emulation at all, you might need to consider that | Since the application simulated is running in your computer, and there is no hardware emulation at all, you might need to consider that [http://en.wikipedia.org/wiki/Endianness endianess] bugs will not be triggered. | ||
Latest revision as of 01:42, 24 March 2016
Qt Simulator is fast and lightweight, but is not the same as an emulator, that means, the real OS of the simulated device is not really running, so it has some limitations.
Screen
The screen of the device is not just a trimmed version of your screen, as the device might have a different pixel density (DPI). That's why the simulator has a slider in the "View" section. When the slider is on "Native size", the simulated device on your screen matches the size of the real device, but maybe you will have less pixels of resolution (devices usually have higher). When the slider is on "Native resolution", your simulated device will use as many pixels of your screen as are available on the real device.
Architecture
Since the application simulated is running in your computer, and there is no hardware emulation at all, you might need to consider that endianess bugs will not be triggered.