CC3 Feature Suggestions

[ProFantasy]

I have a sheet of trees that includes hills that must be drawn in the proper order, but I want the hills to have different 'effects' than the trees. I could create a 'trees before' sheet etc but some tree sets are in front of some hills and behind others in a nearly continous band that I like.

I think you need 'sub sheet lists" that can have other effects that combine with the current sheet using various blending options.

Sorry if someone already covered this, or there is another way to do this in CC3 that I haven't come across yet.

Regards,
-meleeguy

When we first devised effects, we had to decide between a per entity or per sheet model. You've just hit the downside of the per-sheet method.

The per-sheet model has the advantage of simplicity, ease of use and redraw speed, but lacks the range of possibilities of the per-entity model.

[meleeguy]

If I may ask, I'm interested in what program structure issues (if that is the case) are holding you back since my proposal is algorithmically feasible and to our advantage to see resolved, if possible.

Is it file format related?

Although I am a professional programmer of over 20 years, my interest here is as a hobbyist and I realize you're smart folks who have been on the problem for years.

[loydb]

UI Enhancement - something that indicates whether the "Symbols Choose Their Own Layer" is active, preferably with a toggle switch. I constantly forget to reset it.

[ProFantasy]

If I may ask, I'm interested in what program structure issues (if that is the case) are holding you back since my proposal is algorithmically feasible and to our advantage to see resolved, if possible.

Is it file format related?

Although I am a professional programmer of over 20 years, my interest here is as a hobbyist and I realize you're smart folks who have been on the problem for years.

There are no algorithmic issues. We had a straight choice. Including both options would massively and disproportionately increase the difficulty of managing effects, and the speed at which they rendered, as well as requiring much more programming and significant entity database changes.

Incidentally, we do have a developers 'tool kit and mail list, although it's pretty dead at the moment.