Struct objc2_foundation::NSMutableAttributedString

source · [−]

#[repr(C)]
pub struct NSMutableAttributedString { /* private fields */ }

Expand description

A mutable string that has associated attributes.

See Apple’s documentation.

Implementations

source

impl NSMutableAttributedString

source

pub fn class() -> &'static Class

Get a reference to the Objective-C class NSMutableAttributedString.

source

impl NSMutableAttributedString

Creating mutable attributed strings.

source

pub fn new() -> Id<Self, Owned>

Construct an empty mutable attributed string.

source

pub fn from_nsstring(string: &NSString) -> Id<Self, Owned>

source

pub fn from_attributed_nsstring(
attributed_string: &NSAttributedString
) -> Id<Self, Owned>

source

impl NSMutableAttributedString

Modifying the attributed string.

source

pub fn replace(&mut self, attributed_string: &NSAttributedString)

Replaces the entire attributed string.

Methods from Deref<Target = NSAttributedString>

source

pub fn string(&self) -> Id<NSString, Shared>

Methods from Deref<Target = NSObject>

source

pub fn is_kind_of(&self, cls: &Class) -> bool

Methods from Deref<Target = Object>

source

pub fn class(&self) -> &Class

Dynamically find the class of this object.

source

pub unsafe fn ivar_ptr<T>(&self, name: &str) -> *mut T where
T: Encode,

Returns a pointer to the instance variable / ivar with the given name.

This is similar to [UnsafeCell::get], see that for more information on what is and isn’t safe to do.

Usually you will have defined the instance variable yourself with ClassBuilder::add_ivar, the type of the ivar T must match the type used in that.

Attempting to access or modify private implementation details of a class that you do no control using this is not supported, and may invoke undefined behaviour.

Library implementors are strongly encouraged to expose a safe interface to the ivar.

Panics

May panic if the object has no ivar with the given name. May also panic if the type encoding of the ivar differs from the type encoding of T.

This should purely seen as help while debugging and is not guaranteed (e.g. it may be disabled when debug_assertions are off).

Safety

The object must have an instance variable with the given name, and it must be of type T. Any invariants that the object have assumed about the value of the instance variable must not be violated.

No thread syncronization is done on accesses to the variable, so you must ensure that any access to the returned pointer do not cause data races, and that Rust’s mutability rules are not otherwise violated.

source

pub unsafe fn ivar<T>(&self, name: &str) -> &T where
T: Encode,

Returns a reference to the instance variable with the given name.

See Object::ivar_ptr for more information, including on when this panics.

Safety

The object must have an instance variable with the given name, and it must be of type T.

No thread syncronization is done, so you must ensure that no other thread is concurrently mutating the variable. This requirement can be considered upheld if all mutation happens through Object::ivar_mut (since that takes &mut self).

source

pub unsafe fn get_ivar<T>(&self, name: &str) -> &T where
T: Encode,

👎 Deprecated:

Use Object::ivar instead.

Safety

See Object::ivar.

source

pub unsafe fn ivar_mut<T>(&mut self, name: &str) -> &mut T where
T: Encode,

Returns a mutable reference to the ivar with the given name.

See Object::ivar_ptr for more information, including on when this panics.

Safety

The object must have an instance variable with the given name, and it must be of type T.

This access happens through &mut self, which means we know it to be the only reference, hence you do not need to do any work to ensure that data races do not happen.

source