Notification triggered in the FilenameComponent constructor?


#1

Hi Jules,

I noticed that the last line of the FilenameComponent’s constructor triggers a notification:

There is a third argument to FilenameComponent::setCurrentFile with a default value:

One could think that this is just an unneeded call because there is no listener to the object during the constructor call, but the notification is async, so in the meantime a listener is connected (that’s what I observed, I hope I understanded well what was happening) and notified whereas the user has not done anything at all.

Is this notification useful in the constructor? I think that it’s a bug and that we should add a third argument to the call:

All the best


#2

Good point, thanks - yes, I think you’re right about that, I’ll sort it out…