CE Upd. 14: Cell isn't placed at snap point!

When I place a cell it's placed at the cursor position and not at the snap (tentative) point!  PS: This isn't a problem in Update 13 and I'm using MicroStation "out of the box" - without any custom configuration or apps

Try this:

  1.  Start the Place cell tool and choose a cell to be placed
  2.  Do a snap to an element - fx use key-point snap at the end of a line to place the cell origin 
  3.  Before you Accept move the cursor away from the snap point ...notice that if you're using AccuSnap you can only move the cursor a little bit, otherwise you will "loose" the key-point snap. If you're using the "old" snap you're free to move the cursor as long as you wish.
  4.  Now hit Accept (data) and notice that the cell is being placed at the cursor position (not at the end of the line) :-(

Anyone who can confirm this critical problem?

@Bentley: if you can confirm this - please fix this bug A.S.A.P.

Before Accept (after Snap)

After Snap - notice the cell isn't placed at the end of the line :-(

Best regards

Anders

Parents Reply Children
  • Hi Jan and Marco

    It looks like it was the preference file who was causing the problems. With a new .upf it seems to work well ...silly that I didn't thought about this until Jan mentioned it - the .upf is still an old and classic trouble maker ;-)
    Thanks for the tests and replies.

    Best regards

    Anders

  • Anders

    It is also worth noting that each version of CE it is advisable to update the UPF seed file to the new version and recreate the UPF .  They are version specific

    Although the current UPF files will work, it can lead to unknown issues, so good house keeping is to recreate them

    Ian 

  • Ian: I'll maybe have to reconsider my .upf "house keeping" :-)

    I must admit that I don't delete my personal.upf file every time Bentley releases an update. Neither do I always update my seed preference (MS_USERPREFSEED) ...do you really do this approx. twice a year for every application (MicroStation, OpenRoads, OpenCities Map etc.)??
    It's defenately not a win-win situation when I ask my users to delete their .upf so I try to keep this "house keeping" to a minimum ...if it ain't broken, don't fix it!!
    Shouldn''t it be possible for Bentley to develop a more "sustainable" .upf file...?

    Best regards

    Anders

  • I know this is going off topic ......

    I have a UPF seed file for each application.  I never use to worry about it and kept the same upf file, until recently when things started to go wrong more often than not.  

    So as a safety net I now update them.  

    I have these set in my organization level.  Note the enginename, which seperates the application upf's

    MS_USERPREFSEED                                       = $(USER_PREF_SEED)Personal.upf

    MS_DOCKINGPREFSEED                                = $(USER_PREF_SEED)$(_ENGINENAME)DockingPrefSeed.xml

    MS_GROUPPANELPREFSEED                        = $(USER_PREF_SEED)$(_ENGINENAME)GroupPanelPrefSeed.xml

    MS_TASKDIALOGPREFSEED                          = $(USER_PREF_SEED)$(_ENGINENAME)TaskDialogPrefSeed.xml

    MS_RIBBONPREFSSEED                                 = $(USER_PREF_SEED)*.RibbonState.xml

    ian 

  • You're welcome "off topic" :-)
    I have also thought about the need to do something like your suggestion. But I'm a little bit surprised that you seperates the .xml's by _ENGINENAME and not the .upf
    I would have thought it to be "the other way around": that it is the .upf that is the most "fragile" file format and therefore this file have to be "separated" by _ENGINENAME...?

    Regards

    Anders