uniui_core 0.0.4

Basic structures like Signal and Slot for uniui_* crates familiy
Documentation
  • Coverage
  • 100%
    8 out of 8 items documented0 out of 0 items with examples
  • Size
  • Source code size: 9.35 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 1.93 MB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 9s Average build duration of successful builds.
  • all releases: 9s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • maxv-rust

The create provide basic functionality required for uniui_* crates family.

If you are looking information for uniui then the best place to start is (???)[???]

Philosophy

The crate inspired by Qt's signal/slot system. [Signal] can emit data and [Slot] can be connected to the [Signal] to receive data. There is few new concepts like [SlotProxy] and [Property] as well.

There is important difference between uniui and Qt's signal/slots system. [Slot] doesn't activate any peace of code (function/method/etc.) by itself. Instead it have to be pulled from the receiver side (via [SlotImpl::next] or [SlotImpl::last] or etc.). Usually it'll be done by [uniui_gui::Application]'s event loop. Please take a look at [uniui_gui::UWidget] or [uniui_gui::UObject] for slot processing simplification.