Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Project Macros are silently disabled when you use 3 of the 4 methods of opening a project #15659

Closed
qgib opened this issue Sep 24, 2012 · 2 comments
Closed

Project Macros are silently disabled when you use 3 of the 4 methods of opening a project #15659

qgib opened this issue Sep 24, 2012 · 2 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!

Comments

@qgib
Copy link
Contributor

qgib commented Sep 24, 2012

Author Name: Alister Hood (@AlisterH)
Original Redmine Issue: 6406
Affected QGIS version: master

When you open a project that has project macros, if you open it via "File>Open Project", then a notification is displayed saying "security warning: macros have been disabled. Enable".

If you open the project via "File>Open Recent Projects" or by drag-and-drop, or by double-clicking on it in a file manager, then the notification is not displayed; the macros are silently disabled.
@qgib
Copy link
Contributor Author

qgib commented Sep 24, 2012

Author Name: Alister Hood (@AlisterH)

Note: the macros are disabled when not using "File>Open Project" even if "Settings>Options>Enable Macros" is set to always.

@qgib
Copy link
Contributor Author

qgib commented Oct 3, 2012

Author Name: Giuseppe Sucameli (@brushtyler)

Fixed in changeset "bc1bce195edf4c95ff966cfe62aaa410b97a54fe".

  • status_id was changed from Open to Closed

@qgib qgib added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label May 24, 2019
@qgib qgib closed this as completed May 24, 2019
JamesShaeffer pushed a commit to JamesShaeffer/QGIS that referenced this issue Nov 20, 2019
@wonder-sk
Fix crash in node tool after deleting the whole geometry (fixes qgis#…
c093d51 
…15659)

Made sure that both closestVertex() and closestSegment() return negative
distance on error (e.g. with null or emtpy geometry).

Also fixes snapping when dealing with layers with null/invalid geometries
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@qgib