Some properties require a 'click' before fully showing/working about archetype

[tomfulton]

This might (partially) fix #33 also, as it seems to somewhat work on load, just not on addRow

[kgiszewski]

@tomfulton IHMO I think it's the way the some of the jQueryUI properties were wrapped. I can make the slider work properly with Archetype if it's implemented as a directive instead of via the controller.

[kgiszewski]

Check this for reference: https://github.com/umbraco/Umbraco-CMS/blob/b3f6a8c71bdd84e874f0b643373cbbe1aec2fd90/src/Umbraco.Web.UI.Client/src/views/propertyeditors/slider/slider.controller.js#L39

Only fires onload. Should be done via a directive :)

[tomfulton]

Gotcha, makes sense. I just spent some time digging into the DatePicker, and it looks like a similar thing.

When adding a new row, it is executing the DatePicker Controller's JS, but it calls assetService.load(), and it seems the promise never "resolves" (the .then() method never gets executed), so the code to init the widget never gets executed.

What's funny is, the promise resolves as soon as you click anywhere on the body, or even just hovering over the left navbar.

Also, the DatePicker's call to assetService.load() gets all the way here, so I'm not sure why it never actually resolves. Side note: seems to work fine if we pass a scope parameter, even though they use (almost) the same code.

Anyway, I'm in la-land here. Any ideas as to why that method wouldn't finish sometimes?

[tomfulton]

A little more digging:

It might be that $compile doesn't resolve promises. The docs show that some other template related functions don't.

This workaround and calling $rootScope.$apply() seems to fix it, but seems to still break occasionally)

[kgiszewski]

Related? kgiszewski/Umbraco-CMS@6944f25

[tomfulton]

Added weird workaround in #70