- The message box glitch.
Occasionally you might see a message box pop up with a cryptic little message as well a cryptic little label. Just click "OK" and Ophelia will continue.
I used temporary message boxes to make it easier to trace my code in order to see if the named-variables are what they are supposed to be at that spot. In cases where the message boxes don't trigger at all, that's how I know that that branch of code is not working and that I must check the message boxes up the line to see what went wrong. The label on the top of the message box helps me to find that part of the code where this is happening.
When I no longer need the message boxes, I disable them with apostrophes to turn them into comments.
In my copyrighted copy, I had neglected to disable one or two of these message boxes.
- The midnight glitch.
Sometimes if an Excel macro is running at the stroke of midnight, it will freeze up.
If this happens to you, Cinderella, just hit escape and you can find your way out from there. If you know midnight is eminent, just wait until 12:00:01 or so before hitting the "send" button and the midnight glitch won't bother you at all.
Ophelia and most of my Excel games are heavily dependent on random number formulas. On two of the computers that I have used, Excel macros that use random-number formulas will freeze the computer if they are actively running at the stroke of midnight.
The midnight glitch is actually a bigger problem with my Excel games, than with Ophelia herself. I don't even remember if this ever happened to me while using Ophelia. Remember, this glitch will only happen while an Excel macro is actually running, not while you are reading and typing (but maybe speaking) replies to Ophelia's comments.
- The grammar glitches.
Stay tuned for upgrades.
There are a gazillion grammar glitches, which my gazillian grammar macros cannot completely eradicate.
Indeed, when I wrote Ophelia, I got to the point where just about any code in her program that wasn't about English grammar had become frightfully easy to create.
I mean frightfully easy. Ophelia's personality? No code at all. Native. I was starting work on code for her personality, until I realized that Ophelia was developing a native personality of her own, still random and capricious, but far more complex and nuanced than any personality that I could ever write for her.
In contrast to this, I used wheelbarrows and wheelbarrows full of code just to write the macros that convert verbs to the "es" tense, as well as other wheelbarrows and wheelbarrows full of code just for the "ed", the "ing" and "no suffix at all" tenses. Then there are more macros that tell Ophelia when and where to use these macros and there are many more grammar macros besides those, some small, some huge.