[−][src]Struct qt_gui::QPairOfQAccessibleInterfaceQFlagsRelationFlag
The QPair class is a template class that stores a pair of items.
C++ class: QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>
.
The QPair class is a template class that stores a pair of items.
QPair<T1, T2> can be used in your application if the STL pair
type is not available. It stores one value of type T1 and one value of type T2. It can be used as a return value for a function that needs to return two values, or as the value type of a generic container.
Here's an example of a QPair that stores one QString and one double
value:
The components are accessible as public data members called first and second. For example:
pair.first = "pi"; pair.second = 3.14159265358979323846;
Note, however, that it is almost always preferable to define a small struct to hold the result of a function with multiple return values. A struct trivially generalizes to more than two values, and allows more descriptive member names than first
and second
:
struct Variable { QString name; double value; }; Variable v; v.name = "pi"; v.value = 3.14159265358979323846;
The advent of C++11 automatic variable type deduction (auto
) shifts the emphasis from the type name to the name of functions and members. Thus, QPair, like std::pair
and std::tuple
, is mostly useful in generic (template) code, where defining a dedicated type is not possible.
QPair's template data types (T1 and T2) must be assignable data types. You cannot, for example, store a QWidget as a value; instead, store a QWidget *. A few functions have additional requirements; these requirements are documented on a per-function basis.
Methods
impl QPairOfQAccessibleInterfaceQFlagsRelationFlag
[src]
pub unsafe fn copy_from(
&mut self,
other: impl CastInto<Ref<QPairOfQAccessibleInterfaceQFlagsRelationFlag>>
) -> MutRef<QPairOfQAccessibleInterfaceQFlagsRelationFlag>
[src]
&mut self,
other: impl CastInto<Ref<QPairOfQAccessibleInterfaceQFlagsRelationFlag>>
) -> MutRef<QPairOfQAccessibleInterfaceQFlagsRelationFlag>
The QPair class is a template class that stores a pair of items.
Calls C++ function: QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>& QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>::operator=(const QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>& other)
.
The QPair class is a template class that stores a pair of items.
QPair<T1, T2> can be used in your application if the STL pair
type is not available. It stores one value of type T1 and one value of type T2. It can be used as a return value for a function that needs to return two values, or as the value type of a generic container.
Here's an example of a QPair that stores one QString and one double
value:
The components are accessible as public data members called first and second. For example:
pair.first = "pi"; pair.second = 3.14159265358979323846;
Note, however, that it is almost always preferable to define a small struct to hold the result of a function with multiple return values. A struct trivially generalizes to more than two values, and allows more descriptive member names than first
and second
:
struct Variable { QString name; double value; }; Variable v; v.name = "pi"; v.value = 3.14159265358979323846;
The advent of C++11 automatic variable type deduction (auto
) shifts the emphasis from the type name to the name of functions and members. Thus, QPair, like std::pair
and std::tuple
, is mostly useful in generic (template) code, where defining a dedicated type is not possible.
QPair's template data types (T1 and T2) must be assignable data types. You cannot, for example, store a QWidget as a value; instead, store a QWidget *. A few functions have additional requirements; these requirements are documented on a per-function basis.
pub unsafe fn new() -> CppBox<QPairOfQAccessibleInterfaceQFlagsRelationFlag>
[src]
Constructs an empty pair. The first
and second
elements are initialized with default-constructed values.
Calls C++ function: [constructor] void QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>::QPair()
.
Constructs an empty pair. The first
and second
elements are initialized with default-constructed values.
pub unsafe fn new_copy(
other: impl CastInto<Ref<QPairOfQAccessibleInterfaceQFlagsRelationFlag>>
) -> CppBox<QPairOfQAccessibleInterfaceQFlagsRelationFlag>
[src]
other: impl CastInto<Ref<QPairOfQAccessibleInterfaceQFlagsRelationFlag>>
) -> CppBox<QPairOfQAccessibleInterfaceQFlagsRelationFlag>
The QPair class is a template class that stores a pair of items.
Calls C++ function: [constructor] void QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>::QPair(const QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>& other)
.
The QPair class is a template class that stores a pair of items.
QPair<T1, T2> can be used in your application if the STL pair
type is not available. It stores one value of type T1 and one value of type T2. It can be used as a return value for a function that needs to return two values, or as the value type of a generic container.
Here's an example of a QPair that stores one QString and one double
value:
The components are accessible as public data members called first and second. For example:
pair.first = "pi"; pair.second = 3.14159265358979323846;
Note, however, that it is almost always preferable to define a small struct to hold the result of a function with multiple return values. A struct trivially generalizes to more than two values, and allows more descriptive member names than first
and second
:
struct Variable { QString name; double value; }; Variable v; v.name = "pi"; v.value = 3.14159265358979323846;
The advent of C++11 automatic variable type deduction (auto
) shifts the emphasis from the type name to the name of functions and members. Thus, QPair, like std::pair
and std::tuple
, is mostly useful in generic (template) code, where defining a dedicated type is not possible.
QPair's template data types (T1 and T2) must be assignable data types. You cannot, for example, store a QWidget as a value; instead, store a QWidget *. A few functions have additional requirements; these requirements are documented on a per-function basis.
pub unsafe fn swap(
&mut self,
other: impl CastInto<MutRef<QPairOfQAccessibleInterfaceQFlagsRelationFlag>>
)
[src]
&mut self,
other: impl CastInto<MutRef<QPairOfQAccessibleInterfaceQFlagsRelationFlag>>
)
Swaps this pair with other.
Calls C++ function: void QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>::swap(QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>& other)
.
Trait Implementations
impl CppDeletable for QPairOfQAccessibleInterfaceQFlagsRelationFlag
[src]
unsafe fn delete(&mut self)
[src]
The QPair class is a template class that stores a pair of items.
Calls C++ function: [destructor] void QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>::~QPair()
.
The QPair class is a template class that stores a pair of items.
QPair<T1, T2> can be used in your application if the STL pair
type is not available. It stores one value of type T1 and one value of type T2. It can be used as a return value for a function that needs to return two values, or as the value type of a generic container.
Here's an example of a QPair that stores one QString and one double
value:
The components are accessible as public data members called first and second. For example:
pair.first = "pi"; pair.second = 3.14159265358979323846;
Note, however, that it is almost always preferable to define a small struct to hold the result of a function with multiple return values. A struct trivially generalizes to more than two values, and allows more descriptive member names than first
and second
:
struct Variable { QString name; double value; }; Variable v; v.name = "pi"; v.value = 3.14159265358979323846;
The advent of C++11 automatic variable type deduction (auto
) shifts the emphasis from the type name to the name of functions and members. Thus, QPair, like std::pair
and std::tuple
, is mostly useful in generic (template) code, where defining a dedicated type is not possible.
QPair's template data types (T1 and T2) must be assignable data types. You cannot, for example, store a QWidget as a value; instead, store a QWidget *. A few functions have additional requirements; these requirements are documented on a per-function basis.
impl Ge<Ref<QPairOfQAccessibleInterfaceQFlagsRelationFlag>> for QPairOfQAccessibleInterfaceQFlagsRelationFlag
[src]
unsafe fn ge(
&self,
p2: &Ref<QPairOfQAccessibleInterfaceQFlagsRelationFlag>
) -> bool
[src]
&self,
p2: &Ref<QPairOfQAccessibleInterfaceQFlagsRelationFlag>
) -> bool
Returns true
if the numeric Unicode value of c1 is greater than or equal to that of c2; otherwise returns false
.
Calls C++ function: bool operator>=(const QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>& p1, const QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>& p2)
.
Warning: no exact match found in C++ documentation. Below is the C++ documentation for bool operator>=(QChar c1, QChar c2)
:
Returns true
if the numeric Unicode value of c1 is greater than or equal to that of c2; otherwise returns false
.
impl Gt<Ref<QPairOfQAccessibleInterfaceQFlagsRelationFlag>> for QPairOfQAccessibleInterfaceQFlagsRelationFlag
[src]
unsafe fn gt(
&self,
p2: &Ref<QPairOfQAccessibleInterfaceQFlagsRelationFlag>
) -> bool
[src]
&self,
p2: &Ref<QPairOfQAccessibleInterfaceQFlagsRelationFlag>
) -> bool
Calls C++ function: bool operator>(const QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>& p1, const QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>& p2)
.
impl Le<Ref<QPairOfQAccessibleInterfaceQFlagsRelationFlag>> for QPairOfQAccessibleInterfaceQFlagsRelationFlag
[src]
unsafe fn le(
&self,
p2: &Ref<QPairOfQAccessibleInterfaceQFlagsRelationFlag>
) -> bool
[src]
&self,
p2: &Ref<QPairOfQAccessibleInterfaceQFlagsRelationFlag>
) -> bool
Returns true
if the numeric Unicode value of c1 is less than or equal to that of c2; otherwise returns false
.
Calls C++ function: bool operator<=(const QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>& p1, const QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>& p2)
.
Warning: no exact match found in C++ documentation. Below is the C++ documentation for bool operator<=(QChar c1, QChar c2)
:
Returns true
if the numeric Unicode value of c1 is less than or equal to that of c2; otherwise returns false
.
impl Lt<Ref<QPairOfQAccessibleInterfaceQFlagsRelationFlag>> for QPairOfQAccessibleInterfaceQFlagsRelationFlag
[src]
unsafe fn lt(
&self,
p2: &Ref<QPairOfQAccessibleInterfaceQFlagsRelationFlag>
) -> bool
[src]
&self,
p2: &Ref<QPairOfQAccessibleInterfaceQFlagsRelationFlag>
) -> bool
Calls C++ function: bool operator<(const QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>& p1, const QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>& p2)
.
impl PartialEq<Ref<QPairOfQAccessibleInterfaceQFlagsRelationFlag>> for QPairOfQAccessibleInterfaceQFlagsRelationFlag
[src]
fn eq(&self, p2: &Ref<QPairOfQAccessibleInterfaceQFlagsRelationFlag>) -> bool
[src]
Returns true
if c1 and c2 are the same Unicode character; otherwise returns false
.
Calls C++ function: bool operator==(const QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>& p1, const QPair<QAccessibleInterface*, QFlags<QAccessible::RelationFlag>>& p2)
.
Warning: no exact match found in C++ documentation. Below is the C++ documentation for bool operator==(QChar c1, QChar c2)
:
Returns true
if c1 and c2 are the same Unicode character; otherwise returns false
.
#[must_use]
fn ne(&self, other: &Rhs) -> bool
1.0.0[src]
Auto Trait Implementations
impl RefUnwindSafe for QPairOfQAccessibleInterfaceQFlagsRelationFlag
impl Send for QPairOfQAccessibleInterfaceQFlagsRelationFlag
impl Sync for QPairOfQAccessibleInterfaceQFlagsRelationFlag
impl Unpin for QPairOfQAccessibleInterfaceQFlagsRelationFlag
impl UnwindSafe for QPairOfQAccessibleInterfaceQFlagsRelationFlag
Blanket Implementations
impl<T> Any for T where
T: 'static + ?Sized,
[src]
T: 'static + ?Sized,
impl<T> Borrow<T> for T where
T: ?Sized,
[src]
T: ?Sized,
impl<T> BorrowMut<T> for T where
T: ?Sized,
[src]
T: ?Sized,
fn borrow_mut(&mut self) -> &mut T
[src]
impl<T, U> CastInto<U> for T where
U: CastFrom<T>,
[src]
U: CastFrom<T>,
impl<T> From<T> for T
[src]
impl<T, U> Into<U> for T where
U: From<T>,
[src]
U: From<T>,
impl<T> StaticUpcast<T> for T
[src]
unsafe fn static_upcast(ptr: Ptr<T>) -> Ptr<T>
[src]
unsafe fn static_upcast_mut(ptr: MutPtr<T>) -> MutPtr<T>
[src]
impl<T, U> TryFrom<U> for T where
U: Into<T>,
[src]
U: Into<T>,
type Error = Infallible
The type returned in the event of a conversion error.
fn try_from(value: U) -> Result<T, <T as TryFrom<U>>::Error>
[src]
impl<T, U> TryInto<U> for T where
U: TryFrom<T>,
[src]
U: TryFrom<T>,