Convert.ToChar in HTML5 Viewer

Mark Norbury

15. Januar 2015 09:25

I've noticed some inconsistent behaviour when using the Convert.ToChar(13) carriage return character in a workflow.

I'm concatenating a set of strings and using Convert.ToChar(13) as a carriage return character between them.  In the Silverlight Viewer these display OK just as I want them to whether I'm using a DisplayHyperlink or an Alert.

Running the same workflow in the HTML5 Viewer gives varying results.

If I place my results string in the 'Message' argument of a DisplayHyperlink the Convert.ToChar(13) characters are completely ignored and all the text appear on one line.

If I place my results string in the 'Text' argument of an Alert some of the Convert.ToChar(13) characters are included but some are ignored.

Is there something else I should be using instead of Convert.ToChar(13) to get a carriage return character for the HTML5 Viewer or is there some setting I need to change in its configuration?

Thanks.

0

• 

  Mark Norbury

  16. Januar 2015 07:14

  I've also tried Environment.NewLine and this is not supported in the HTML5 Viewer either.

  This looks a lot like a bug.

  0
• 

  Mark Norbury

  17. Januar 2015 03:42

  I've reported this to Latitude and the bug ticket is GVH-3310.

  After having done some more testing, I've found that the bug only occurs with certain activities.

  In the HTML5 Viewer,

  In a DisplayForm the Convert.ToChar(13) and Environment.NewLine will both work (using Runtime Modifications);

  In an Alert, the Environment.NewLine will work, but not the Convert.ToChar(13);

  For the Message in a DisplayHyperlink, neither of them will work.

  In the Silverlight Viewer, the Convert.ToChar(13) and Environment.NewLine will work with all three of these activities.

  I hope this helps anyone else who comes across these issues.

  0
• 

  Permanently deleted user

  21. März 2017 17:47

  What is the status of this?  I have also found that the Custom Geometry Instructions in the DisplayCaptureGeometry tool do not respect Environment.NewLine either - it is ignored.

   

   

  0
• 

  Amanda Frech

  11. Mai 2017 23:36

  Hi everyone,

   

  GVH-3310 is still an open issue.  The viewer isn't deliberately stripping out these characters, rather your internet browser is collapsing the whitespace.  In some cases it may be possible to apply custom formatting to prevent this from happening.  For the DisplayCaptureGeometry activity, a workaround is posted here (https://support.geocortex.com/essentialsGSCForum?sub-nav=forum&main-nav=essentials&#!/feedtype=SINGLE_QUESTION_DETAIL&id=906600000000AvtAAE) .

   

  Hope that helps,

   

  Amanda

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.