Xamarin.WindowView is just a rough port to C# of justasm's WindowView, in fact, I copied his readme too!
Window as in windowsill.
ImageView that can be panned around by tilting your device, as if you were looking
through a window.
Add it to your project using NuGet:
Install-Package Xamarin.WindowView -Pre
Use in place of an
ImageView. Example XML layout file:
<Jmedeisis.WindowView.WindowView android:layout_width="match_parent" android:layout_height="match_parent" android:src="@drawable/my_image" />
Please refer to the included sample application project for a complete example.
You will typically want to configure the following attributes for the
wwv_max_pitch- maximum angle (in degrees) from origin for vertical device tilts. Default - 30°
wwv_max_roll- maximum angle (in degrees) from origin for horizontal device tilts. Default - 30°
wwv_vertical_origin- (in degrees) when device pitch equals this value, the image is centered vertically. Default - 0°
wwv_horizontal_origin- (in degrees) when device roll equals this value, the image is centered horizontally. Default - 0°
You may also want to configure more advanced attributes:
Relative(default). Specifies whether device tilt should be tracked with respect to
Absoluteworld coordinates (i.e. pitch, roll w.r.t. ground plane) or with respect to the device orientation when
WindowViewis created, which
WindowViewrefers to as the 'orientation origin'. If using the latter, i.e.
Relative, you may use
WindowView#resetOrientationOrigin(boolean)to set the orientation origin to that of the device when the method is called.
Proportional(default). Specifies how much the image is translated in response to device tilt. If
Proportional, the image moves within the full range defined by
max_roll, with the extremities of the image visible when device pitch / roll is at those angles. If
Constant, the image moves a constant amount per unit of tilt which is defined by
max_constant_translation, achieved when pitch / roll are at
wwv_max_constant_translation- see above. Default - 150dp
wwv_sensor_sampling_period- the desired rate of sensor events. In microseconds or one of
slow. If using microsecond values, higher values result in slower sensor updates. Directly related to the rate at which
WindowViewupdates in response to device tilt.
Automatic(default). Specifies whether
WindowViewis responsible for when tilt motion tracking starts and stops. If
WindowViewworks out of the box and requires no extra configuration. If
Manual, you must explicitly start and stop tilt motion tracking. You have two options:
WindowView#stopTiltTracking(), e.g. in your
WindowView#detachTiltTracking(TiltSensor). This approach is recommended when using multiple
WindowViews in a single logical layout. The externally managed
TiltSensorshould be started and stopped using
<Jmedeisis.WindowView.WindowView android:layout_width="match_parent" android:layout_height="match_parent" android:src="@drawable/my_image" app:wwv_tilt_sensor_mode="Manual" app:wwv_orientation_mode="Relative" app:wwv_translate_mode="Constant" app:wwv_max_constant_translation="100dp" app:wwv_sensor_sampling_period="fast" app:wwv_max_pitch="15" app:wwv_max_roll="15" app:wwv_vertical_origin="0" app:wwv_horizontal_origin="0" />
- Only supports the CENTER_CROP scale type.
Works for API levels 9+.
Pull requests are welcome and encouraged for bugfixes and features such as:
- adaptive smoothing filters tuned for different sensor accuracy and rates
- bi-directional image panning
Xamarin.WindowView is licensed under the terms of the MIT License.