Forum

Hi,

I have a problem with CExtLabel.  The text in all of my CExtLabel controls appear with strikethrough (and sometimes also underlined).  This doesn’t happen for texts in any other control in my application.

When I simply replace CExtLabel with CStatic, the text appear properly.  

I have tried various things to pinpoint the reason for this problem, including a brute force SetFont call for the object, but to no avail.

I hope you can tell me what I do wrong.

Thanks in advance

Finn Arildsen

...after installation of a 2.25.1 patch. I opened Prof-UIS project in VC and made a clean build of all Prof-UIS libs. Problem with CExtLabel disappeared.

Actually I wondered why patch setup did not recompile libraries...

Neither the full library setup nor the patch "knows" which library configuration you really need. Besides, if we completely rebuild all library configurations, it will eat tens of gigabytes of the disk space. That is why the automatic library build is not performed by installation programs.

Hm, but setup program for the "normal" version has an option to build libraries. At least it was so in the previous version...

Dear Finn,

We have not yet encountered such a bug. Of course, we are very interested in helping you and clarifying what causes the problem. Could you let us take a look at your sample project?

Thanks for your very swift response.   I’m actually working on conversion of a 100K lines project, so it’s not straightforward for me to extract a sample project.

However, I’ll see if I can recreate the problem in a sample project.  This will be in a couple of weeks, though, due to other obligations. 

BTW, what governs a CExtLabel’s use of fonts?   Is there anything I may have touched that I shouldn’t have ?  (Not that I think I have intentionally touched anything wrt fonts).

We have no idea why the label’s font is damaged but you can find it out yourself by debugging the CExtLabel::OnDrawLabelText method’s code. You need to see which font is used for painting the text and why it is striked out and/or underlined.

Thanks for your response.

Having been away for some days, before I got round to creating a small example, Dmitry’s posting directed me to the solution, which is to rebuild the libraries.

Thankfully, rebuilding the libraries is a simple solution.  However, this reminds me that I have problems with the Integration Wizard.  If I let the IW build the libraries on installation, it always ends up hanging while building the second library in the list, and I have to slay it.   I haven’t been able to figure out the reason for this problem, and it something I can circumvent by just building the libraries directly from Visual Studio, so I don’t think it’s a problem I wish to pursue.  BTW, it was the same with 2.23.  Nevertheless, I thought I’d mention it, and I’ll be glad to provide any further information if you need it.