Macro's new and old unable to edit[?]
Wickwill opened this issue · 8 comments
To add, this only came up in the latest release. Was working perfectly last night.
Can you export the macro and add it here so I can have a look?
TimothyLuke
… On 5 Jul 2021, at 8:41 pm, Wickwill ***@***.***> wrote:
To add, this only came up in the latest release. Was working perfectly last night.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
If the original author exports this read only and its shared it’s unable to be edited. What I need to be able to see is what has made this think that it’s read only and as it doesn’t happen at my end I need that export to pull apart.
TimothyLuke
… On 5 Jul 2021, at 8:41 pm, Wickwill ***@***.***> wrote:
To add, this only came up in the latest release. Was working perfectly last night.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
It is not even letting me get to that point. Even on a newly created macro that message comes up and does not allow me to save it. Cannot amend any of my old macros either due to that message. This is across the board on all my characters and all my macro's. That message is at the bottom of the screen and I can do nothing
Export is on the previous menu screen before you get to the editor.
Alternatively can you upload your GSE.lua file from
`c:\path\to\wow\_retail\WTF\Account\YOURACCOUNTNAME\SavedVariables` you may
need to rename it to GSE.lua.txt or make it a Zip file to add to Github
…On Mon, 5 Jul 2021 at 20:46, Wickwill ***@***.***> wrote:
It is not even letting me get to that point. Even on a newly created macro
that message comes up and does not allow me to save it. Cannot amend any of
my old macros either due to that message. This is across the board on all
my characters and all my macro's. That message is at the bottom of the
screen and I can do nothing
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#933 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEMCFJGSZJLYMFRK3TG7GDTWGICFANCNFSM472QG4WA>
.
--
*Timothy Minahan**M* 0406 413 680 | *E ***@***.***
I cant replicate this - maybe 3.0.17 has fixed it mysteriously? Without your settings file (requested earlier) I cant tell what is going on on your end.