mudlet-makers team mailing list archive

[Vadim Peretokin <vperetokin@xxxxxxxxx>]

The issue seems to be that it was used in a non-trigger context.
insertText() on its own doesn't handle it very well, inserting boxes
instead of newlines when used as such.

When used within a trigger context, both insertText and cinertText
behave the same, with the exception of cinsertText() adding its value.
See screenshot.

** Summary changed:

- line breaks in cecho() show but the line order is reversed
+ cinsert() doesn't respect inserted new lines

** Attachment added: "Selection_455.png"
   https://bugs.launchpad.net/mudlet/+bug/1214836/+attachment/3846327/+files/Selection_455.png

** Changed in: mudlet
       Status: In Progress => Invalid

-- 
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1214836

Title:
  cinsert() doesn't respect inserted new lines

Status in Mudlet the MUD client:
  Invalid

Bug description:
  See test script:

  echo("\nTEST PART1: C-API echo & insert functions: <blue>STARTING<light_blue> test#1<green>...\n")
  echo("<red>red text<blue>blue text<green>and some green text\n")
  moveCursor(10,getLineCount()-1)
  insertText("***INSERTING***<orange>orange<pink>pink<purple>purple\ncontinuing on next line#1<green>test 2\ncontinuing on next line#2<blue>test3")

  cecho("\nTEST PART2: mudlet-lua cecho & cinsert:<blue>STARTING<light_blue> test#1<green>...\n")
  cecho("<red>red text<blue>blue text<green>and some green text\n")
  moveCursor(10,getLineCount()-1)
  cinsertText("***INSERTING***<orange>orange<pink>pink<purple>purple\ncontinuing on next line#1<green>test 2\ncontinuing on next line#2<blue>test3")

  echo("\nRESULT: cinsert() doesn't respect inserted new lines\n")

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1214836/+subscriptions