When I am selecting a reference (in the references overview window) it sometimes automaticly selects more references when I move down/up. How can I turn this off? If I want to select more then 1 reference I want to use shift and select.
Hi Nico, i tried to replicate this in MicroStation version 10.17.02.61 and the only reason I found for this behaviour may be related to combination of selecting + dragging the left mouse button over references list.
Unfortunately this feature cannot be turned off.
Zeno
It's hard to replicate this because Microstation sometimes does it but mostly doesn't. I am not talking about selecting and dragging by the way.
Hi Nico,
Please provide Version being used and if possible provide a simple testcase.
It may be that you have a Master file, that contains a Reference and its associated Nested References that is Self Referenced.
When the Self Reference is selected in the Reference Dialog (List on Right Hand Side of Dialog) the Reference and its Nested References will be Selected.
Instead you can expand the Hierarchy, Select the Self Reference, then on the Right Hand Side select the Required Nested Reference
Does this help?
Thanks for your answer, but this is not what I mean. I have the latest version, but I had the same issue whith the version before this one. What I mean is when you just select a reference and move down, sometimes microstation continues to select all the references you hoover over (and I am not talking about dragging over them) and sometimes it doesn't do this.
Apparently, I was able to reproduce the described behaviour:
If I select one of the references from the dialog and I’m quick enough to move my cursor/mouse over the other references of the list, the first and all subsequent references are highlighted.
Same operation done slower is ok.
It is quite tricky and not always possible replicate this behaviour. I am not sure why, but it could be related to latency of selection action which, due to the speed of the command, is interpreted as the “select and drag” option. I would need to verify this with developer team to find a possible explanation.
This does not seem to be a big issue, but i will investigate the matter with the developers.
I don't think that there is currently an option to disable this behaviour.