Quote: "
Not really. The API calls will no doubt be different for different operating systems. So maybe it's just a bug in the AppGameKit Windows code. I'm not knocking AppGameKit but it needs to be fixed one way or another."
Point taken.
Quote: "
How do you initialize the string of the the window title?"
He gave his example in the first post.
This looks like tier 2, so not my forte.
My suggestion was to use a variable and construct the string with chr() 's
Not sure how you guys would do that in tier 2, or if it would make a difference with Windblows 10, but I use chr() 's to construct string variables when I do not want to have the string visible in the bytecode.
Just thinking that maybe the quotes are messing with it reading all the characters (i know that doesn't make sense, but neither does this error) , so the suggestion was to use a string variable instead of quoted text. (even a string variable without the construct may be worth trying)
Sorry I cannot test for you as I am not using Windblows 10 (I should install AppGameKit on my other laptop, but I would need to buy another copy)
If I could have tested, then I would have done so before making the suggestion as to not waste your time testing something that will not work.
(suggestion was just a thought of a potential work around if the quoted text is causing the bug)
Coding things my way since 1981 -- Currently using AppGameKit V2 Tier 1
