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

[Guest]

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

[Arnis Gubins]

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.

[AxialInfo]

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.

[Guest]

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

[AxialInfo]

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.

[Guest]

So, Sheila ... I sat down this morning to write up a bug-report, and at a given moment suddenly wondered "Can this be a classic pbcak?" Well, yes and no.

Hard to reproduce, but at least once I've observed the following behaviour:

When you select an existing condition from the list and see the Add/edit condition tag dialogue, the default button/action is (as you might hope) [Edit]. That is, after all, what you're trying to do; you've selected an existing condition. But changing the style or colour setting deftly switches the default button/action from [Edit] to [Add] – which is not what you're trying to do, given the tag name hasn't changed. And when you then inattentively hit Return instead of thoughtfully clicking on [Edit] ... the system correctly informs you that the tag-name already exists.

Sneaky, at best! but I suppose the workaround is just to click on [Edit] instead of hitting Return.

N

[Guest]

Farther unsatisfactory behaviour from the Variables pod, so I'll add it to this thread … I wanted to update a variable yesterday, so started by selecting it in the big Variables panel. Then I clicked on the Edit button in the toolbar. The result was the Add/edit Variable panel with no variable information in; from farther experiment, it seems you have to have to have an instance selected before you can use the Add/edit panel.