The Jade 2025 release focuses on modernising the developer experience and helping you build faster, smarter, and more scalable applications.
Sometimes I will code something that causes a runtime exception: 1307 : Cannot pass an exclusive subobject reference to this method.
The compiler doesn't give any warning I have coded something this way, collection.add(someExclusiveObject) compiles as normal.
When looking at 'someExclusiveObject' Property Details, the only hint I get that it's an Exclusive is an extremely subtle "non-virtual" at the bottom of the details. Compare this to a Non-Exclusive which has the words "non-virtual embedded" at the bottom, this is confusing.
It's very hard to catch this mistake before runtime. Some ideas:
- Property Details "non-virtual" / "non-virtual embedded" have a suffix afterwards to stipulate which one of these phrases is the 'Exclusive' version.
- Can the compiler check this and error instead of waiting for me to get a runtime error.
- Hover-text (and maybe IDE colour option) to help identify these while I'm coding.
Thanks
Guest
I think anything to help make it easier to understand is appreciated.
Addendum... When you open "Painter" and someone else is using the form, you get the option to see the form in read-only mode.
Currently when clicking on properties while a Form is in use, I can't see the GUI. Is it possible to have this GUI as read-only when viewing properties?
Even better... This could be in a tab next to [Property Details]? Then the information I'm looking for is visible - without extra clicks and without popups - in a consistent UI.
We could implement the first suggestion but the latter two are not possible because determining whether something is exclusive cannot be determined until runtime.