it's the same code! isn't it?
-
Don't you hate when you're porting something, and you stare at the same section of non-working code over and over, comparing it to the reference source, and not seeing any meaningful difference? Yet it doesn't work. In this case, no sign of life. That has been my morning. Partial updates simply are not working on this display and I can't figure out for the life of me why. The only "decent" documentation for the display is the source code that it shipped with. This kind of thing is the absolute worst. Excepting the other things that are also the absolute worst.
To err is human. Fortune favors the monsters.
Get up and go for a walk. Give your subconscious a chance to work on it. I've often had the answer during or shortly after a walk that I couldn't "see" before. Cheers!
Sincerely, -Mark mamiller@mhemail.org
-
Get up and go for a walk. Give your subconscious a chance to work on it. I've often had the answer during or shortly after a walk that I couldn't "see" before. Cheers!
Sincerely, -Mark mamiller@mhemail.org
Yeah, I switched gears. I'll pick it up again later. I've already got some ideas on how to either narrow the problem, or uncover a larger issue. That's a start.
To err is human. Fortune favors the monsters.
-
Had a similar issue with a text string copied from somewhere (Word? Web page) and inserted into VS. Was failing horribly. After a lot of time spent on this, it turns out a non-printable character was in that string.... Once I manually re-typed the string, worked just fine....