Build failed in Jenkins: royale-compiler-integration-tests #337

See Changes: -- [...truncated 156.44 KB...] [junit] [junit] Jan 04, 2020 5:48:16 AM

Build failed in Jenkins: royale-compiler-integration-tests #336

See Changes: -- [...truncated 159.09 KB...] [junit] scanning for overrides: ApplicationBase [junit] scanning for overrides:

About Jewel Table component

Hi, one of the things for 1.0 was ensuring APIs are ok. When I created Jewel Table I left with API methods I was not happy "selectedItem"/"selectedItemProperty"or comment I found now the time to revisit the component and right now I don't see the reason I didn't like it at that time. Maybe

Build failed in Jenkins: royale-compiler-integration-tests #335

See Changes: -- [...truncated 157.72 KB...] [junit] [junit] Jan 03, 2020 3:11:28 PM

Build failed in Jenkins: royale-compiler-integration-tests #334

See Changes: -- [...truncated 157.08 KB...] [junit] [junit] Jan 03, 2020 8:34:42 AM

Re: Starting to look at Bindings

Ah, ok, it might be to support either HTML or plain text content. IIRC, there are a couple of ITextModels and one takes the time to initialize _text = "" and one doesn't. The component sets that care less about PAYG can use the NonNull TextModel by default. -Alex On 1/3/20, 12:04 AM,

Re: Starting to look at Bindings

What happens if the html property is set? In that case, I think the textNode does not reference anything valid. That’s probably broken wither way though… > On Jan 3, 2020, at 7:55 AM, Alex Harui wrote: > > I noticed that "if (textNode)" the other day and wondered why it was there > but