Author: sirksel
Posted: Fri Sep 02, 2016 5:07 pm (GMT -6)
Mr. Ghisler, thank you for the quick response and offer to troubleshoot. This turns out not to be a bug. I was about to paste my [Colors] for you, and then decided to try it in a fresh portable TC installation. I am glad I tested it because it worked fine -- hence your difficulty in recreating the behavior.
I spent a while commenting out sections of my wincmd.ini until I came upon some settings causing the problem -- whose existence I had completely forgotten about. In my [Configuration] section, the SelectionFocus and InactiveFocus were hindering my intentions, but operating just as you had so carefully documented! :) Long ago, I had set them as $3000000 to get the solid-line behavior. After later changing my color scheme, that embedded RGB of black was overruling my new cursor color settings in the particular instances I described in my original post.
I'm hopeful that this post might be a help to someone who is experiencing the same issue, but forgets (like I do) the prior wincmd.ini options they set. Thanks again for your time, and sorry for the false alarm.
Posted: Fri Sep 02, 2016 5:07 pm (GMT -6)
Mr. Ghisler, thank you for the quick response and offer to troubleshoot. This turns out not to be a bug. I was about to paste my [Colors] for you, and then decided to try it in a fresh portable TC installation. I am glad I tested it because it worked fine -- hence your difficulty in recreating the behavior.
I spent a while commenting out sections of my wincmd.ini until I came upon some settings causing the problem -- whose existence I had completely forgotten about. In my [Configuration] section, the SelectionFocus and InactiveFocus were hindering my intentions, but operating just as you had so carefully documented! :) Long ago, I had set them as $3000000 to get the solid-line behavior. After later changing my color scheme, that embedded RGB of black was overruling my new cursor color settings in the particular instances I described in my original post.
I'm hopeful that this post might be a help to someone who is experiencing the same issue, but forgets (like I do) the prior wincmd.ini options they set. Thanks again for your time, and sorry for the false alarm.