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 new file dialog ignores SM configurations with a custom scripting directory - even though I only have one SM profile configured, the new file dialog still insists on creating the SP file in /sourcepawn/scripts, instead of the directory where my compiler is according to my active profile.
Is it possible to at least have the option to have new SP files default to being created in the same directory as your profile's scripting directory?
The text was updated successfully, but these errors were encountered:
Hexer10
added a commit
to SPCodeOrg/SPCode
that referenced
this issue
Apr 10, 2020
The new file dialog ignores SM configurations with a custom scripting directory - even though I only have one SM profile configured, the new file dialog still insists on creating the SP file in /sourcepawn/scripts, instead of the directory where my compiler is according to my active profile.
Is it possible to at least have the option to have new SP files default to being created in the same directory as your profile's scripting directory?
The text was updated successfully, but these errors were encountered: