Comment 10 for bug 1377401

Would I be right in thinking that this thing "like Topsy" has got too
big (and complex) to track everything that is going on.

You might like to check, but I think all the OptionsArea stuff is just
useless cruft (all dlgOptionsArea*.h; mpOptionsArea* pointers in
dlgTRiggerEditor and all the options_area_*.ui forms) this is not doing
anything to harm or cause the problems but they do not seem to be adding
anything to the project in this area AFAICS.

I vaguely recall AC suggesting that he wanted to go over the trigger
editor - I take it that he is not currently able to add any insight into
this matter.

I'm guessing but I'm beginning to suspect that each of the
{Action|Alias|Keys|Scripts|Triggers}MainArea classes (and possibly the
Vars one as well) will have to gain an isDirty flag which is set when
any content (after we have picked out what *is* content - does
"mpActionsMainArea->lineEdit_action_icon" count, for instance) is
modified and use that to determine whether to save the current
content... (that is compounded by the complexity of whether the current
content is a "group" or "item" {branch vs leaf node???})

I'm guessing we want something for the delta version if not before, 8-(

On 08/01/15 00:04, Vadim Peretokin wrote:
> Agreed - that's what I did. I ended up with a loop through that didn't seem
> fixable.