cnativeapi 0.4.0

cnativeapi: ^0.4.0 copied to clipboard

native_view_backend_t and native_view_is_backend_supported, native_view_set_default_backend, native_view_get_default_backend, native_view_get_backend.

Raw bindings for the view module (native_view_*, native_label_*, native_button_*, native_text_field_*, native_image_view_*, native_window_get_content_view) and native_edge_insets_t.

cnativeapi is now a plain Dart package instead of a Flutter FFI plugin, so it works in Dart command-line apps as well as Flutter apps. A build hook (hook/build.dart) compiles the nativeapi core with the target's toolchain in place of the per-platform CMake, CocoaPods and SwiftPM projects.

Breaking: the bindings are top-level @Native functions. The CNativeApiBindings class and the cnativeApiBindings instance are gone; call native_window_create() instead of cnativeApiBindings.native_window_create(). Enum-typed struct fields are now also readable as the Dart enum; the raw value is <field>AsInt.

Breaking: every function taking a callback, and every struct with a callback field, takes a native_release_user_data_t after its user_data (nullptr if there is nothing to release). The core calls it exactly once, on the main thread, once it can no longer call the callback.

The WinUI 3 backend on Windows (NATIVEAPI_ENABLE_WINUI3) is not built by the hook; the Win32 implementations are used.

native_window_set_content_under_title_bar, native_window_is_content_under_title_bar and native_window_is_content_under_title_bar_supported are new, and NATIVE_TITLE_BAR_STYLE_HIDDEN now hides the window control buttons on macOS too. See the nativeapi changelog.

native_window_set_visual_effect returns whether the effect is in force; native_window_is_visual_effect_supported is new, and so are the effects MICA_ALT, HUD, POPOVER and MENU. The effect is read from the native window, shows in a Flutter window on macOS, and on Windows Blur is a plain blur-behind that works on Windows 10. See the nativeapi changelog.

LaunchAtLogin on Windows: an app running from an MSIX package gets a shortcut in the user's Startup folder, because the Run registry key an MSIX container writes is virtualized and never read. IsEnabled() also reads Explorer's StartupApproved\Run flag and Enable() clears it, so an entry the user switched off in Task Manager is not reported as enabled and enabling it again really enables it. The registry is written through the wide API, so a non-ASCII identifier or path survives.

LaunchAtLogin on macOS: setProgram() naming the running application registers that application whatever the identifier says, instead of failing because the identifier does not name a bundled login item helper. Arguments are recorded but never delivered — SMAppService starts the app bundle, nothing else — where before any argument made enable() fail.