1) Yea if you typed the name of a variable into a local variable correctly, it will apply the content into the host variable just like i did abovemaybe it's a bug concerning global variables, @MacroDroidDev will say what happens but it would be good to clarify 2 things
1. you say you used a [v=...] inside a variable and it gives the impression that
you did this by editingt he local variable and including it inside the text
I don't think this works so perhaps you really mean that
you used the "set variable" action ??
2. you say you converted a global variable to a local variable (near the end of your post), how did you do this ?? there is no conversion mechanism, so ..
by deleting the global variable and making a new local variable ? or by keeping the original global variable and creating a new local variable with same name
ThanksThanks for the clarification, this is just a display issue so will be an easy fix and I will update for the next release.
about 2. you are right, I had forgotten this since I don't use much global variables
however, when I make a test macro for 1. and use a new global variable it doesn't show me that it's used by the macro (it's just an unused variable)
about 1.
yes , I did a test macro and what you say does work (!)
but after first use the [v=...] has been replaced ,
but if instead I use a [lv=...] it stays in the variable text
so.. it's not an issue about conversion but rather that this replacement
(this magic replacement )
is permanent if using a reference to a global variable
but is not permanent and the reference stays for a local variable
I think @MacroDroidDev didn't have in mind such use of variable reference (see my notice in 1. in that the global variable appears to be free and not used by any macro)
but nevertheless he will be able to make this trick work repeatedly for global variables too
about 2. you are right, I had forgotten this since I don't use much global variables
however, when I make a test macro for 1. and use a new global variable it doesn't show me that it's used by the macro (it's just an unused variable)
about 1.
yes , I did a test macro and what you say does work (!)
but after first use the [v=...] has been replaced ,
but if instead I use a [lv=...] it stays in the variable text
so.. it's not an issue about conversion but rather that this replacement
(this magic replacement )
is permanent if using a reference to a global variable
but is not permanent and the reference stays for a local variable
I think @MacroDroidDev didn't have in mind such use of variable reference (see my notice in 1. in that the global variable appears to be free and not used by any macro)
but nevertheless he will be able to
Hi @MacroDroidDev.Thanks
Looking forward for the update
okThere has been no update since I wrote, so the fix isn't available yet.
There has been no update since I wrote, so the fix isn't available yet.
I think maybe Jamie has other things to do, read post #7 and #12Hi @MacroDroidDev
Please I wish to know if I should reconfigure my macro to use local variables as I was seriously anticipating this thread to be resolved.
Am still curious to know why it's pending..
PLEASE REPLY
Still NO RESPONDS...????? Quite unlike Jamie
Please keep in mind that other people including Jamie do not need to have time for you just right now or in any other moment you have a free time and want a response. They are responding you because they want and have time for it, not because they must or need to. Please respect that.