The ViewData API solves the problem of having a UI-specific state, not part of
the data, survive domain reload and Editor restarts. The idea is to have a
persistent data store on each EditorWindow
. Each VisualElement
has a
viewDataKey
that must be set in order to enable ViewData
persistence.
To enable view data persistence for an element that supports it, set the viewDataKey
to a unique key within your EditorWindow
.
Persistence of view data is enabled as long as an element has a valid viewDataKey
. The only exception is when an element is in the shadow tree of its parent and not a physical child of its logical parent’s contentContainer
. In this case, the parent must have its own viewDataKey
set for the children in its shadow tree to be persisted.
For example, in ScrollView
, each scroll bar has its own viewDataKey
that is unique within the ScrollView
element. When the ScrollView
has no key set,
the scroll bars are not persisted. Otherwise, the scroll bars will combine their viewDataKey
with the parent viewDataKey
to create a globally unique key.
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More information
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising. Some 3rd party video providers do not allow video views without targeting cookies. If you are experiencing difficulty viewing a video, you will need to set your cookie preferences for targeting to yes if you wish to view videos from these providers. Unity does not control this.
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.