DYE save error on startup with Streamline skin, just after enabling DYE.

[decentjohn]

I received this DYE error on startup with Streamline skin, just after enabling DYE.

I suspect the problem is incomplete metadata, as the DYE UI hasn't yet been used. Probably (?) DYE should not throw an error? Or should Streamline prepopulate the metadata with blanks?

can't read "src_data(bean_brand)": no such element in array
can't read "src_data(bean_brand)": no such element in array
    while executing
"if { $data($field) ne $src_data($field) } {
					set changes($field) $data($field)
				}"
    (procedure "save_description" line 25)
    invoked from within
"save_description"
    (procedure "::dui::pages::DYE::hide" line 4)
    invoked from within
"::dui::pages::DYE::hide DYE off"
    ("after" script)

[ebengoechea]

DYE should not even start with new skins for which I've added no support/test it works. It has always been like that, and an error page was shown and the plugin disabled. But Damian insisted I remove the restrictions to facilitate things to people doing DSx2 forks or something, so I did.

So, if it's the time for DYE integration with Streamline, I will check it, but otherwise for this beta it would be better not to allow it under Streamline.

[ebengoechea]

Looking at my answer, and upon reflection, unless I change a few things to make sure that at least DYE doesn't fail and doesn't do weird things with new or unsupported skins, it would likely be sensible not to enable it by default at the moment. Sorry I hadn't realized before.

[decentjohn]

no problem, and I don't think the next app development cycle will be as long as the one we're just finishing.