Page 1 of 1
rom/createpath.lua not working
Posted: Thu Sep 10, 2009 2:49 pm
by ginokid
Did you change the code to create a path???
Just updated the bot & when I try to create a path now using rom/createpath.lua I get this error.
Code: Select all
Thu Sep 10 15:37:00 2009 : ...gs/gino/Desktop/micromacro/scripts/rom/functions.lua:79: bad argument #1 to '?' (string expected, got nil)
Thu Sep 10 15:37:00 2009 : Execution error: Runtime error
Thu Sep 10 15:43:06 2009 : Executing script 'createpath.lua'
==================================================
Thu Sep 10 15:43:06 2009 : ...gs/gino/Desktop/micromacro/scripts/rom/functions.lua:79: bad argument #1 to '?' (string expected, got nil)
Thu Sep 10 15:43:06 2009 : Execution error: Runtime error
Re: rom/createpath.lua not working
Posted: Thu Sep 10, 2009 3:00 pm
by Administrator
This is most likely caused by a broken update. Make sure that all files are up to date (if they aren't marked green, they didn't update properly). Any filed marked red should be deleted first, and then run the update again.
Re: rom/createpath.lua not working
Posted: Thu Sep 10, 2009 3:15 pm
by ginokid
I deleted the whole rom folder, then updated to version 230. All files and folders have a green check mark.
Hasn't fixed the problem.
What should I do?
Re: rom/createpath.lua not working
Posted: Thu Sep 10, 2009 3:37 pm
by d003232
ginokid wrote:I deleted the whole rom folder, then updated to version 230. All files and folders have a green check mark.
Hasn't fixed the problem.
What should I do?
Yes, it's a bug.
I inserted
Code: Select all
attach(getWin()); -- <<<< THAT LINE
startMacro(main, true);
to solve another problem with the hotkey MACRO. Now that bug comes if there are more then one RoM windows.
@admin: can you look what's the right soulution? Without the attach the hotkey will not send correct. Runus means
here that
would be a solution. But I don't understand what's that doing?
EDIT: I suppose loading the settings earlier would be help?
Re: rom/createpath.lua not working
Posted: Thu Sep 10, 2009 3:44 pm
by d003232
SVN 231 should fix it.