Documentation:OCLOperators RootObject: Difference between revisions

OCLOperators RootObject

Revision as of 06:33, 6 March 2023

selfVM.RootObject gives access to the object rooting a ViewModel instance. This is read-only and you can use it like this:

selfVM.RootObject->safeCast(Thing).SomeString:='a new value'

Why is the selfVM.RootObject not typed but requires a cast to be used with the real root? Because OCL is a statically typed language and selfVM is context sensitive, meaning it is available in all ViewModels - there is no 1 answer to what type the RootObject should have. If you are in the context of a ViewModel, you will however know what type it has and can safely cast.

This page was edited 91 days ago on 02/10/2024. What links here

@@ Line 1: / Line 1: @@
-selfVM.RootObject gives access to the object rooting a viewmodel instance. This is readonly and you can use it like this:
+selfVM.RootObject gives access to the object rooting a ViewModel instance. This is read-only and you can use it like this:
 selfVM.RootObject->safeCast(Thing).SomeString:='a new value'
-? Why is the selfVM.RootObject not typed and require a cast to be used with the real root? Because OCL is a statically typed language and selfVM is context sensitive in the meaning it is available in all viewmodels - and there is no 1 answer to what type the RootObject should have. If you are in the context of a viewmodel you will however know what type it has and can safely cast.
+Why is the selfVM.RootObject not typed but requires a cast to be used with the real root? Because OCL is a statically typed language and selfVM is context sensitive, meaning it is available in all ViewModels - there is no 1 answer to what type the RootObject should have. If you are in the context of a ViewModel, you will however know what type it has and can safely cast.
 [[Category:OCLOperators]]