Problem with TEXT command

Hello,

I posted a support request on May 23rd regarding a problem I encountered with the TEXT command. I have yet to receive a response from tech support. Could anyone confirm what I'm seeing?
This is from my post to support:

**This problem occurs if you use any justification except the default (LEFT). Here is the sequence to produce the problem:

  1. Start the TEXT command.
  2. Choose any other justification option, for example MIDDLE.
  3. Pick the start point.
  4. Start typing. The text preview does not appear at the point chosen. It appears at the origin (0,0).
  5. Press ENTER to complete the line.
  6. The text now appears at the point chosen.
  7. This repeats until the command is ended.

If the default LEFT justification is accepted, the command behaves normally; the text appears at the point selected.
**
This didn't occur in the V18.1 release. This problem occurs on both my home and work computers. Both computers are running Windows 7 SP1, 64 bit, and are current with Windows updates.
I am running the latest version of BricsCAD CLASSIC, 64 bit.

Comments

  • Confirmed! Strange behavior indeed

  • I have some issues with DTEXT. Maybe related?
    v18.2.14 on Win7 Pro.

    DTEXT [Enter]
    Command Line prompt: “Text: Style/Align/Fit/Center/Middle/Right/Justify/:”
    SELECT (point of text)
    Command Line prompt: “Height of text <4">:” 6 [Enter]
    Command Line prompt: “A positive value is needed. Please try again.” 6 [Enter]
    Command Line prompt: “Rotation angle of text <0.0000>:” [Enter]
    Command Line prompt: “Error occurred in mtext editor: Invalid input”

    Prompt History:
    DTEXT
    Text: Style/Align/Fit/Center/Middle/Right/Justify/:
    Height of text <4">:
    A positive value is needed. Please try again.
    Height of text <4">: 6
    Rotation angle of text <0.0000>:
    Error occurred in mtext editor: Invalid input
  • Filed a Support Request re: above. 24 hr.s later, response:
    Thank you for your report. We are aware of this issue, an internal task is already created and our development team is working on it depending of priorities.

This discussion has been closed.