Really big problem with FloorInd

[Anonymous]

hi all
I have problem with API_Elem_Head.FloorInd data.

when i insert new story to plan between existings, my object's FloorInd's changed, but door/windows have wrong FloorInd!! Why this can be?

example:
when i create new Door in room on this new Story, it have wrong FloorInd !

but in Plan (connected throw ODBC driver), it have correct Story element assigned to this Door

API: 12.2156

this really huge problem for our product, please, really need help
how I can get correct FloorInd, where mistake?

[Anonymous]

Anyone had same problem or maybe know solution.. or it's really GS bug?

[Anonymous]

no1 answered..

owner Wall have correct story level, so we use it instead of element story index (for doors and windows)

no help, but thx for all for reading and mb thinking about this problem

p.s. seems it bug (

[Laszlo Nagy]

Very few Users are programmers.
If you get no answer here, you should then report it to your local reseller.

[Anonymous]

Hi,

I am thinking this is because, we may have multi level windows and doors.

For Example if you inserted multi level window (1) in floor_0 and its height is more than the story height then it will be extended in floor_1 also. If you inserted multi level window (2) in floor_1 and its lower is (-ve) value then it will be extended in floor_0 also.

So in our organization we are working with story heights (example: If the floor_0 = 2600 high, floor_1 = 2400 high and joist = 300 mm high then
door.lower < 2600 then it is inserted in floor_0,
door.lower > 2600 then it is inserted in floor_1 and
door.lower < 2600 and door.lower+door.height >2600 then it is inserted in floor_0 and is multilevel winow) or owner floor in order to find the floorind of Door and window elements.

Ranga

[Anonymous]

Hi, Ranga Rao
and in our case, windows/doors located exactly on 1 floor

thx for answer
we use owner(Wall) floorInd from now (and it's seems correct in all cases)


in our solution with height there are may be some troubles, when story's height = 0....
eah.. it's seem's like mistake, but our costumers have such plans