topic Re: Typical Floor Scheduling in Libraries & objects

Typical Floor Scheduling

Anonymous — Wed, 24 May 2023 10:32:38 GMT

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

Re: Typical Floor Scheduling

Anonymous — Wed, 10 Dec 2014 03:17:46 GMT

Hey Tom

Are you doing units within the overall building and are you saving the modules as .pln or just .mod?

Re: Typical Floor Scheduling

Anonymous — Wed, 10 Dec 2014 03:28:50 GMT

Hi Kristian,
We are using a separate pln authoring file, which has many stories to represent all the seperate typical files.
We then publish to mod

Re: Typical Floor Scheduling

Anonymous — Wed, 10 Dec 2014 06:16:50 GMT

Ahhh ok
Unfortunately the mod file wont pass any of that info into
the master folder!You might be able to create a second parameter
that calls the story number as just text from your story_name parameter. (say, story_name_txt)
If you use the GLOB_MODPAR_NAME you should be able to get it to fill out once... maybe??

So something like
IF GLOB_MODPAR_NAME = story_name THEN
PARAMETERS story_name_txt = story_name
ENDIF

I'm not at a machine with AC on it at the moment to test it mate but it's worth a shot!

Re: Typical Floor Scheduling

Anonymous — Thu, 11 Dec 2014 02:20:58 GMT

No luck.
I just find it really odd that when I check the parameters of the object in my combined main file, the parameter looks good.
When I check the schedule which is calling up the exact same parameter, it reads a different number. I don't understand how this can happen

Re: Typical Floor Scheduling

Anonymous — Thu, 11 Dec 2014 02:28:09 GMT

The thing is when you use modules, it essentially drops the project settings
of the original file and adopts the environment of the file its brought into!

I'll have a dig at it tonight mate and see if I can come up with a way around it!

Re: Typical Floor Scheduling

Anonymous — Thu, 11 Dec 2014 02:33:46 GMT

Thanks Kristian,
I actually want it to drop the properties of the mod file so it reads the story settings of the main file.
I guess it would make sence if the parameter read the same number in plan and schedule. Im confussed

Re: Typical Floor Scheduling

Anonymous — Thu, 11 Dec 2014 04:47:00 GMT

ahhhhhh ok now I see what you're doing mate
I just did a quick test with another object.
Where in the script have you placed the request and parameter value? (Master, 2D, Parameter etc)
I did mine in the master and I can get it to keep the info from the authoring file (which could be handy) but I can't get the 00 like you have mate!

Re: Typical Floor Scheduling

Anonymous — Thu, 11 Dec 2014 04:54:28 GMT

Thanks for looking at this Kristian,
I am doing everything to do with this in the parameter script. I think I have over complicated things by also doing something such as if index = 0 then output = "00".
I will try simplifying and moving to the master script and hope I can pull the number from the main file
Cheers

Re: Typical Floor Scheduling

Anonymous — Thu, 11 Dec 2014 07:10:55 GMT

That's no sweat at all mate!
I'ma actually working on some module stuff myself so I've just tagged it into that!

Re: Typical Floor Scheduling

Anonymous — Fri, 12 Dec 2014 04:29:20 GMT

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

Re: Typical Floor Scheduling

Anonymous — Fri, 12 Dec 2014 04:51:16 GMT

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

Re: Typical Floor Scheduling

Anonymous — Fri, 12 Dec 2014 06:44:25 GMT

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

Re: Typical Floor Scheduling

Piotr Dobrowolski — Fri, 12 Dec 2014 09:42:10 GMT

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