You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The notification when opening a project that contains macro doesn't warn enough about the potential risks. I'd suggest that the "Enable macro" link opens a message box explaining more in detail what could happen if the code was hostile. Bonus point would be a way to inspect the code before giving the consent or not.
Apparently from @elpaso feedback, same issue with code in forms
The text was updated successfully, but these errors were encountered:
rouault
added
the
Bug
Either a bug report, or a bug fix. Let's hope for the latter!
label
Oct 30, 2019
IMHO this ticket should perhaps be labelled as a feature request, the report mentioned from the users mailing list is referring to a crash which is in fact a bug, be this ticket is more like a enhancement.
Related to "social experiment" https://lists.osgeo.org/pipermail/qgis-user/2019-October/044155.html
The notification when opening a project that contains macro doesn't warn enough about the potential risks. I'd suggest that the "Enable macro" link opens a message box explaining more in detail what could happen if the code was hostile. Bonus point would be a way to inspect the code before giving the consent or not.
Apparently from @elpaso feedback, same issue with code in forms
The text was updated successfully, but these errors were encountered: