BTW, allowing the Designer to specify a package and/or sub-package name would be exceedingly handy, as well. If we import multiple Catalyst generated MXPLs into Builder to use within a single project, they all get lumped into a single "Components" package. This will surely result in multiple components with the same name on a large project.
I agree about IDs. I've filed an enhancement request. No promises, though =).
Allowing custom organization in the Library panel is also on our radar.
Excellent -- thanks a lot, Adam.
I assume that when you say "custom organization in the Library panel" that will carry over to the organization of the components' packages upon export. Is that correct?
1 person found this helpful
That would obviously be desirable. But we try not to make any specific promises about potential features.
Understandable. Thanks again, Adam.