Patrick Näf
Patrick Näf
With the unification of UI layouts (#371) the first approach now seems to be possible again.
Find out how it is possible that BoardViewMetrics makes its calculations with a coordinate system that has its origin in the upper-left corner, but drawing with Core Graphics still works?...
First, let's make sure that it is really the NSCoding archiving process that is slow. Measurements taken with the "Time Profiler" instrument on an iPhone 3GS: - Scenario 1: Make...
Measurements taken on an iPad 2nd generation - For scenario 1: `SaveApplicationStateCommand` takes about 100ms. - For scenario 3: The entire operation of discarding the move takes about 420ms.
Conclusion: Since there is no simple and obvious optimization, I let this issue rest for the moment in the hope that improved device capabilities will cover up the problem.
Closing this issue as it appears to have been obsoleted by performance gains of new devices.
Issue #113 has hints about optimization potential.
Some notes: - Calculations must be based on the view size of the BoardViewController main view - The resulting canvas size must then be used to size BoardView - When...
This has top priority. There were several super-negative customer reviews in the past concerning the "stone distance from fingertip" feature, so this really must be addressed soon.
The Google Earth app has a simple-looking tutorial that could serve as inspiration.