Hi Aliak The design of the UserManager was ****plain**** bad. It was reintroducing this ugly facade singleton pattern (monolitic and global) like the old Preferences class that we fight a lot with alain and finally replace by setting. It was a mistake that I did not have the time to review the code. (BTW we were pushing too much code in the system without a good review). Now this period is over. The solution of the new approach should be the same than settings. - first any part that should be user managed should do it locally and introduce its own hooks to do so but be self-contained: exactly like Setting. A class uses class variables and check its class variables when doing something. - It means that as a client of the part I can change some accesses. - then we decorate such user-managed hooks and provide tools. Stef
Bloc is broken because UserManager is no longer in the image. (it was removed on 14th of August) For some reason there is a check:
UserManager default canDropOSFile
this check is used in #dropFiles:
What is alternative or does it make sense to remove the check?
Cheers, Alex