Skip to main content
June 11, 2009
Question

"condition already exist" – except it doesn't [FM 9.0p230]

  • June 11, 2009
  • 2 replies
  • 953 views

Here is the list of condition tags defined in the document I'm working on, extracted from a .mif copy:

  <CTag `deleted_012006'>
  <CTag `deleted_012007'>
  <CTag `deleted_022007'>
  <CTag `deleted_032006'>
  <CTag `deleted_032007'>
  <CTag `deleted_042006'>
  <CTag `FM8_SYSTEM_HIDEELEMENT'>
  <CTag `FM8_TRACK_CHANGES_ADDED'>
  <CTag `FM8_TRACK_CHANGES_DELETED'>
  <CTag `new_012006'>
  <CTag `new_012007'>
  <CTag `new_022006'>
  <CTag `new_022007'>
  <CTag `new_032006'>
  <CTag `new_042006'>
  <CTag `updated_022007'>
  <CTag `updated_032006'>
  <CTag `updated_042006'>

So can someone explain why trying to set up a new tag "new_032009" netts me a dull thud and the strangely-worded message "Specified tag already exist"? To make it that bit more annoying, this supposedly pre-existent tag does not show up in either the Conditional Text pod (?) or the list of conditions in the status bar after I press esc, q, C

Thanks in advance!

NGN

    This topic has been closed for replies.

    2 replies

    June 11, 2009

    I get the error message when adding a new condition when there is a condition highlighted in the condition pod -- if I click somewhere in the pod to un--highlight / un-select then the new condition is created.

    June 15, 2009

    Thanks for the tip, Sheila – yes, adding a new condition does seem to work when you carefully ensure no pre-existing condition is selected. I had similar problems with editing a pre-existing condition, though the latest try succeeded. Don't know why, but I suppose I should be encouraged that it _did_ and just persist next time.

    N

    June 15, 2009

    I should have added that I think it would be worth a bug report, though, because it does seem like an incorrect behavior and one that would be easily triggered, causing much confusion.

    Arnis Gubins
    Inspiring
    June 11, 2009

    Niels,

    Did updating to the latest p237 release change anything for this situation?

    The only other thing I can think of is that there might be a tag name size limit. You already have a "new_032006" tag that except for the last digit is the same as the one that you're trying to add.