Announcement

Collapse
No announcement yet.

HS3 difference

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • HS3 difference

    When data is written to the log in HS3, unlike HS2, it does not strip the html and instead decodes it to hex.

    This means that log entries are harder to read, and with BLLAN an example would be:

    Nov-03 00:01:28 BLLAN Info [Log Entry Contains Chars Converted to Hex in Brackets{}]Computer - Network Humax --{3E} 2 PING failures

    a) does anyone know a get round for this to get clean messages or
    b) Bob: is there any chance of a minor change to strip the html before outputting the message?

    Simon
    Last edited by simonog; November 3rd, 2013, 04:40 AM.

  • #2
    In the latest release Simon, I also eliminated that long text string that is prepended and shortened the hex to show as 0x## so it won't take up as much space anymore.

    But yes, unless the built-in color options are used (hs.WriteLogEx) which are for the entire line, special characters (such as some HTML tag characters) are converted so it's best not to use HTML.
    Regards,

    Rick Tinker (a.k.a. "Tink")

    Comment


    • #3
      Originally posted by Rick Tinker View Post
      In the latest release Simon, I also eliminated that long text string that is prepended and shortened the hex to show as 0x## so it won't take up as much space anymore.

      But yes, unless the built-in color options are used (hs.WriteLogEx) which are for the entire line, special characters (such as some HTML tag characters) are converted so it's best not to use HTML.
      Rick
      Thank you. that's definitely better from a log perspective!

      it does still need script/PlugIn authors to modify how they log things a little bit.

      Simon

      Comment

      Working...
      X