Yehnfikm8Gq Posted January 1, 2010 Report Posted January 1, 2010 I had problems with a converted macro which turned out to be due to an incorrect conversion: Original ME3.........If Variable %T1% contains "[H:\" Converted to MEPro........If Variable %T[1]% Contains "[H:\\" Removing one of the backslashes cured the problem I'm sure I saw something somewhere about this but I can't find it and Help search doesn't allow the \\ search string. Is it a bug or is it in a dire warning list somewhere? Quote
rberq Posted January 1, 2010 Report Posted January 1, 2010 Report it as a bug. I came across a couple of conversion issues which were quickly fixed after I reported them. Quote
Cory Posted January 4, 2010 Report Posted January 4, 2010 I have converted many ME3 macros and have never seen this double backslash. However I have not converted any with the past couple of versions. Can you create a simple ME3 macro and reproduce? Then attach that with your bugrep. However I often find things that look like bugs and after I try to create a simple example I find that the problem was something completely unexpected. Quote
Yehnfikm8Gq Posted January 4, 2010 Author Report Posted January 4, 2010 Thanks for the responses. I sent a bug report a few days ago. I re-sent today with a simple macro. Same issue. Considering the difference in variables format between the two versions, it may not like the square bracket in a text string. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.