-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tried to set a font today with SetFont(), didn't work #4
Comments
Hi, i had a little use for this feature so it is in pretty early state and can parse only comma separated values. One exception is table that should be specified as t=TableName. Tablename can be dot separateed. So you use quotes and my parser will just parse them as is and pass string with quotes down the function and you also have comma inside a string so my parser will just create 4 args instead of 3. I'll try to fix this as soon as i can. Thank you for reporting. And right now you can hack it yourself if you want to Lines 1021 to 1044 in 6c26ac8
Lines 915 to 924 in 6c26ac8
Where FromStrToObject is Lines 359 to 372 in 6c26ac8
|
Thanks for reply. I tried to pass only "Fonts\FRIZQT__.TTF", 17 into the arguments field, didn't work either. So the problem is not only to related to commas being inside strings. I am not really sure what exactly is the problem tho. |
don't use quotes, try Fonts\FRIZQT__.TTF, 17 i don't have access to wow/windows pc right now, will fix this as soon as i can |
Hi, i tried to use this addon to call a function with arguments today. I typed "Fonts\FRIZQT__.TTF", 11, "OUTLINE, MONOCHROME" into the arguments field and pressed enter. Since this Function doesn't give any feedback if the font was successfully changed i called GetFont() afterwards. It showed me that the SetFont() wasn't successful. Calling the same function per /run with the same arguments worked. I guess it has something todo with the handling of the \ character.
The text was updated successfully, but these errors were encountered: