Typical Floor Scheduling

[Anonymous]

Hi,
I have created Zones, Doors and Windows which display the story number as part of a custom field Output Zone Number, Output Door Number or Output Window Number.

This is so that an element that is placed in a typical hotlink file, will show its relevant story number when brought into the main file.

I have done this by using the 'index' for the story number in
Request("story", "",index,story_name)


For Example, Zone Output Number = 'story number'-'Zone Number
05-001

All works well in plan, that as the typical module is copied up the building, the zone number looks as I like
i.e.
05-001
06-001
07-001
etc.

However when I open the schedule and add the custom parameter, it doesn't pick up the same number, it picks up the story number of the hotlink
ie
00-001
00-001
00-001

Is there a way around this to pick up the main file story in schedules??
I'm stumped

Thanks
Tom

[Anonymous]

So, have moved my script into the master but still with problems that the parameter updates in the object settings, but the schedule is still not updating

[Anonymous]

Just to explain what I have done,

I have this in the master script (I know the 'parameters' command should be in the parameter script, however I have tried all conditions)

aaa= Request("story", "",index,story_name)
parameters storyno = str(index,2,0)+""

But as the attached image, the parameters update in the main file, but not the schedule in the same file?? I am assuming I am missing something very simple.
This is quite a frustrating stumbling block at the moment

[Anonymous]

Tom just as a test, break one of the hotlinks and then open the schedule!
See if it just because of the static state of the module!
Make sure you save just before you break it though!
Just in case! haa ha ha haaa

[Piotr Dobrowolski]

It is unfortunately known bug

I had this in my zone stamp

The problem is that the parameter change in the schedule (I mean the users' parameters change not the default ones) must be some kind of triggered to change.
I had a dummy parameter in the zone stamp that was put into a dummy schedule (containing this parameter only) and changing this parameter (it was an changing back after running) the all custom values were going to the "main" schedule quite correctly.

Best Regards,
Piotr