Microstation Has Stopped Working

[Rene Seiler]

Inmy DgnElementSetTool, I'm placing a cell at the projection of the cursor to the picked element. The cell gets placed, but the association is not correct - the cell has a dashed outline. What am I missing? I can successfully create a Dependency Linkage, but not an AssociativePoint....

I have site levels (heights) for a project, and I am wanting to model the terrain. The project is a small deck off the back of an existing house, and there will be a lot of instances where we are doing small residential alterations through to medium commercial (e.g schools) which don't usually require a full geotechnical survey or contours, we have a level reader, zero it at the floor level and then take the readings of the ground levels around the building resulting in points.

What is the best way to model this, and then be able to alter it if we are excavating, adding retaining, flattening a site etc, and so that it can show up as a line when adding sections and elevations to the models and creating drawings? I have tried to find a tutorial, but the available information for how to do this includes complex georeferencing (which we never use)

Would love to hear the methods for smaller scale terrain modelling and your suggestions, please see images added for reference to the said project. If someone could also add a step by step description/images that would be fantastic and much appreciated!

I created a VBA Macro Code in Excel to automate 3D drawing of a Box Girder Bridge. At some instances, readily available commands like "Isometric View , Right Isometric View" , etc are not sufficient to help my code locate to do certain operations. Therefore I need to have a code to locate my view point using the coordinates of the object.

The MicroStationAPI DialogItemHookHandler class lets us write simpler hook handlers for MicroStation dialog items. They let you avoid the giant MDL switch statement in your procedural hook handler code.

The ComboBox and ListBox dialog items share the use of a ListModel to display information to the user. You must always deallocate the ListModel in the _OnDestroy() dialog item event. When you read 'you must always' in a C++ context, a solution is often a class member implementation. In this case, I've written a C++ template class specialised for ComboBox and ListBox dialog item hook handlers. Read more about the ListModelManager.

If I have an element (e.g. line or linesting) and a point (DPoint3d), I can use ClosestPointBounded(DPoint3dR, CurveLocationDetailR, bool,bool) to obtain a CurveDetail, then use FractionToPoint() to obtain the "closest point on the curve". The returned "fraction" seems to be the same regardless if I pass "true" or "false" as the last two parameters, as does the "distance from space point" value. I am looking for some way to ultimately determine if the returned "closest point" lies "on" or "off" the start/end of the subject curve. Is it possible?

In V8i we can use class Bentley.Internal.MicroStation.ReferenceAttachment (in ustation.dll) to ask attributes of attachment like NestMode and IgnoreWhenLiveNesting. But in Connect Edition this Class can not be found any more. Is the Class ReferenceAttachment still vaild in Connect Edition?

I can and probably will just sprinkle "If .IsSharedCellElement set x = .AsSharedCellElement else set x = .AsCellElement" throughout the code unless there's a smarter way, since I only care about name, ID, and traversing subelements.

But what is the best way to deal with tags as text elements without changing the file? What I have currently is a partial text reading tool based off TextElement.Boundary and TextElement.Rotation, that lets you use a shape as a fence to assign meaning to text and read arbitrary substrings without breaking up cells or text.

Tags, of course, do not return property "Boundary", but I somehow must get their true dimensions in order to determine which part of the tag the user has placed the selection mask over. It might work to use "Range" instead, but is there any way to estimate how much difference there will be between properties "Range" and "Boundary" at various rotations (particularly, as a percent of a character's width or total string length)? If "Range" is the same as "Boundary" or uniformly different in all directions, "Range" could still work on tags, but I am not clear what the difference is between the two in the first place.

In MicroStation CONNECT Edition, I have using IViewUpdateEvents events . It's rapidly calling again and again.After some time MicroStation CONNECT shows stopped working.I am using same code in microstation,it's working fine.I am using following code in my mvba file class.Kindly to find out, if any issues in code for microstation connect edition.

I want to dimension several widths and have it be a single dimension. I want to start from zero each time I click a data point. The picture on the left is what I do not want. The one on the right is what I do want. Is it in the advanced tab of my Dimension Styles dialog? Sorry if this is the wrong forum for this question.

I am not a programmer and although I am learning VBA, I have been unsuccessful in trying to replicate the same MDL app function in VBA. If someone can easily modify and recompile my old V8i MDL app so it can work in my CONNECT edition, that will be great thanks. or if someone can guide me to write a VBA version of that MDL app, that'll be very beneficial for my learning too.

To cut long story short, I've been thrown into an admin role for Microstation and I have setup all of our workspaces, worksets etc, as per our organisation need. That end of the setup is all fine and working (although I might ask for help if I come across some issues).

For now, my issue is with mdl app. We used to use one of the custom mdl application for our everyday use and I realise mdl application from v8i needs to be re-written from scratch to work in connect edition. This is where the problem is I am not a programmer (neither do i have access to BDN). Although I am learning how to use vba within Microstation, I have been unsuccessful in trying to reproduce in vba.

This is the vba codes I have written but since I need these 2 lines of text appear in a mouse pointer with 1.8mm height & width so users can place it wherever they want, it started to get bit complicated for me.

Normaly, I delete elements by selecting them with a window

(PowerSelector tool), and then press the delete key on the key bord or

press the delete tool, in the main tool box.With some drawings it isn't possible to delete elements with de method

mentioned above.In the problem drawings: The only way to delete items is by pressing

the delete button in the main toolbox, followed by clicking on the

element I want to delete. I have to repeat this for every single

element I want to delete.I think there must be a setting in microstation wich is able to lock

elements with the purpose to protect elements from beiing deleted by a

sertain user or so.Does anyone have the same problems as me? or does anyone knows a

solution for this problem?I'm looking forward to any reaction on this messageThanks in advance!Wibo Posthumus

If you are able to delete them using the delete tool, then select the

elements, then they are not locked. The problem may be with the element

selection tool or powerselector. The powerselector "window" tool uses an

inside lock by default. If you click the "window" icon again, the tool will

work in an overlap mode. That way you get everything inside and everything

touching your window.Does this only happen in 3D files?

--

Steve Young

Minds Eye Technical Services

"Wibo Posthumus" wrote in message

news:bdf3737.01112...@posting.google.com...

I am not sure I follow exactly what you are asking, but if you are saying

that there are some elements that you can select, but not delete, then it is

possible that these elements are "Locked". If you use the Analyse Element

(the I - Info Icon) and select one of these elements, then it should tell

you if the element is "Locked" or "Not locked". You can change it there, but

it will be quicker to select all the elements and issue the key-in command

"Change Unlock" and this will unlock any locked elements.If the problem is that you have elements that you cannot select with the

selection tools, then there may be some corruption of these elements. Have

you tried selecting them with the old select element tool or the

PowerSelector 2point (line) tool? Your other option maybe to enclose the

elements with a fence and delete them using the fence delete tool with the

inside or overlap setting as appropriate. If all else fails, you might have

to run the file through EDG to see if there is any corruption, and if so,

fix it up.HTHDennis Barker

Innovision Technologies Pty Ltd

www.innovis.com.au

The design file you are working in may have settings saved with 'Selection

Set Lock : OFF'. Turn it back on with the following keyin... "LOCK SELECTION ON"Save settings (FILEDESIGN), so that next time you open file 'Selection Set

Lock : ON', remains on.-Chuck Gummo

i'm not sure if you resolved your problem but in the old days of

version 3 and 4 if you place a fence around all your design file

elements, set aa=360 and then rotate original if forces microstation

to re-write the design file.

you may then have access to all your elements.john o dwyer

Hello, I don't understand why but since 3 days my excel file shutdown when I trying to run a macro which running without any problem before. I've seen diffrents other problems like I can't write a value directly into a cell, or I write it in an other cells and when valid it is enter to the correct cells I've selected or I have to enter the value from the general bar after select the cell I want to write into . It's very strange, I never had these problem before . I've to run my excel file on an other computer ,to start it after restart my computer, but same problems remain. Does anybody can help me ? Thanks .

3a8082e126