WPF RadRichtextbox error when inserting sample text using =rand(1)

[Dex]

Hi,

I've written a xaml for adding annotation through a RadRichTextBox on contents in a Word document. But when I try to insert sample text using =rand() im getting the error attached.

Any idea why this is happening? I tried to put break points in every method and events on the code behind but the error shows up even before it executes any of my code.

Thanks,
Dexter

[Boby]

Hi Dex,
Acutally this is an issue with the random text generator and is independent from your annotations. We will fix the issue for the next version of the control. With the current version the only supported random text generation is with the command "=rand(p, s)", where p is the number of paragraphs, and s is the number of sentences in one paragraph.

Please, excuse us for the inconvenience. We have added points to your account for the report. Don't hesitate to contact us if you have other questions.

Regards,
Boby
Telerik

 

 

[Dex]

Hi Boby,

Thanks for the response. Can I know when will this be fixed? On what release?

Thanks,
Dex

[Boby]

Hi Dex,
The change is already in the code-base, and will be published in the next LIB and next official release - 2014 Q2 SP1

Regards,
Boby
Telerik

 

 

[Anselmo]

Hi Boby,

I grabbed the latest WPF RichText box release (2014.2.729.40) and it seems that the =rand(x) is not yet fixed. On my first try issuing the "=rand(1)" it generates the random text but when I tried again there is a dispatch error encountered. See my screencast: 

http://screencast.com/t/FCSHrVMLKMm

Not sure if I did something wrong. Also I didn't see on your release notes for this release version (http://www.telerik.com/VersionNotes.aspx?id=3866) that the "=random(x)" is also fixed. Can you confirm this? If its currently not fixed can we know when will this be available? 

BTW - Dex is also me :)


Thanks,
Anselmo

[Anselmo]

Hi Boby,

After integrating it with our application it works fine now. Not sure why it is throwing an error on my sample project. But anyway its good that it has been addressed.

Thanks,
Anselmo

[Boby]

Hello Anselmo ,
It seems that we have missed to mention this fix in the release notes, but we have included it for the 2014 Q2 SP1 release.

That said, I am not able to reproduce the problem with the latest release. The steps that I perform on my side are:

• Type 'rand(1)' and press enter
• Type 'rand(2,1)' and press enter

Can you confirm that these are the exact steps at your side? If yes, I would suggest you to open a separate support ticket and send us sample application that reproduces the problem, accompanied with exact steps to reproduce.

One possible issue reason that comes to my mind is different culture settings, but I've tried several without success in crash reproduction.

Regards,
Boby
Telerik