winit/src/platform_impl/ios/mod.rs

112 lines
3 KiB
Rust
Raw Normal View History

2016-12-13 07:28:30 -06:00
//! iOS support
//!
//! # Building app
//! To build ios app you will need rustc built for this targets:
//!
//! - armv7-apple-ios
//! - armv7s-apple-ios
//! - i386-apple-ios
//! - aarch64-apple-ios
//! - x86_64-apple-ios
//!
//! Then
//!
//! ```
//! cargo build --target=...
//! ```
//! The simplest way to integrate your app into xcode environment is to build it
//! as a static library. Wrap your main function and export it.
//!
//! ```rust, ignore
//! #[no_mangle]
2018-06-14 19:42:18 -04:00
//! pub extern fn start_winit_app() {
2016-12-13 07:28:30 -06:00
//! start_inner()
//! }
//!
//! fn start_inner() {
//! ...
//! }
//! ```
//!
2018-06-14 19:42:18 -04:00
//! Compile project and then drag resulting .a into Xcode project. Add winit.h to xcode.
2016-12-13 07:28:30 -06:00
//!
2016-12-13 07:37:13 -06:00
//! ```ignore
2018-06-14 19:42:18 -04:00
//! void start_winit_app();
2016-12-13 07:28:30 -06:00
//! ```
//!
2018-06-14 19:42:18 -04:00
//! Use start_winit_app inside your xcode's main function.
2016-12-13 07:28:30 -06:00
//!
//!
//! # App lifecycle and events
//!
//! iOS environment is very different from other platforms and you must be very
//! careful with it's events. Familiarize yourself with
//! [app lifecycle](https://developer.apple.com/library/ios/documentation/UIKit/Reference/UIApplicationDelegate_Protocol/).
//!
//!
2018-06-14 19:42:18 -04:00
//! This is how those event are represented in winit:
2016-12-13 07:28:30 -06:00
//!
//! - applicationDidBecomeActive is Resumed
//! - applicationWillResignActive is Suspended
//! - applicationWillTerminate is LoopExiting
2016-12-13 07:28:30 -06:00
//!
//! Keep in mind that after LoopExiting event is received every attempt to draw with
2016-12-13 07:28:30 -06:00
//! opengl will result in segfault.
//!
//! Also note that app may not receive the LoopExiting event if suspended; it might be SIGKILL'ed.
2016-12-13 07:28:30 -06:00
#![cfg(ios_platform)]
2022-06-10 13:43:33 +03:00
#![allow(clippy::let_unit_value)]
2015-06-05 16:38:21 +03:00
mod app_state;
mod event_loop;
mod ffi;
mod monitor;
mod uikit;
mod view;
mod window;
use std::fmt;
use crate::event::DeviceId as RootDeviceId;
pub(crate) use self::{
event_loop::{
ActiveEventLoop, EventLoop, EventLoopProxy, OwnedDisplayHandle,
PlatformSpecificEventLoopAttributes,
},
monitor::{MonitorHandle, VideoModeHandle},
window::{PlatformSpecificWindowAttributes, Window, WindowId},
};
pub(crate) use crate::cursor::NoCustomCursor as PlatformCustomCursor;
2023-12-22 22:20:41 +01:00
pub(crate) use crate::cursor::NoCustomCursor as PlatformCustomCursorBuilder;
pub(crate) use crate::icon::NoIcon as PlatformIcon;
pub(crate) use crate::platform_impl::Fullscreen;
/// There is no way to detect which device that performed a certain event in
/// UIKit (i.e. you can't differentiate between different external keyboards,
/// or whether it was the main touchscreen, assistive technologies, or some
/// other pointer device that caused a touch event).
#[derive(Debug, Copy, Clone, PartialEq, Eq, PartialOrd, Ord, Hash)]
pub struct DeviceId;
impl DeviceId {
pub const unsafe fn dummy() -> Self {
DeviceId
2016-12-13 07:28:30 -06:00
}
}
pub(crate) const DEVICE_ID: RootDeviceId = RootDeviceId(DeviceId);
#[derive(Debug, Clone, PartialEq, Eq, Hash)]
pub struct KeyEventExtra {}
#[derive(Debug)]
pub enum OsError {}
impl fmt::Display for OsError {
2022-06-10 13:43:33 +03:00
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
write!(f, "os error")
}
}