Wrong handling of CRLF in Caption of Taskdialog-Butotn

BernhardGeyer

When using Mulilline-Text in Commandlink-Text, the extraction of Caption and Note-Text is wrong.

In Methode TLMDCustomTaskDialog.SetupCommandLinks it used LMDLF to separate Text and Note.
But CR ($13) is in Caption and when do TLMDCommandLinkButton.ReCalcHeight, the DrawText-Function use the CR to say that the height must be higher

BernhardGeyer

This is what you get


This is what you expect




(If you dont see images, try to edit comment)

balabuev

Hi,

I'm sorry for delay. I've tryied to play with command link buttons in ther task dialog, but I can't undewrstand what you mean. Can you please send a small demo app to our support e-mail.

balabuev

I think I've got the idea.

But, why you think, that splitting caption and notes with #13#10 is allowed? You should split them with #10 only.

BernhardGeyer

Why? The normal Text-Separation unter Windows ist #13#10.
Its strange that only #10 should be used!

balabuev

Hi,

Really, ElPack implementation just executes standard WinAPI function: TaskDialogIndirect. So, the rule of using only #10 is not our (LMD related) rule. It just how WinAPI works.

Actually, I'm also, can't understand, why #13#10 are not recognized...

BernhardGeyer

I think we should handly it in the LMD-Implementation correctly. WinAPI isn't "intuitive" in this area.