Interactive Schedule: Worked in AC10, doesn't in AC11

[Laura Yanoviak]

Our Door Schedule and Window Schedule IS's from AC10 work fine in AC11, but I cannot get our Area Schedule and Finish Schedule to cooperate! I ran into similar problems when migrating from AC9 to AC10, but they were remedied by recreating the IS.

Now, I can't get anything to work. I've recreated the IS's, I've tried taking the "Additional Parameters" from the extracted library instead of the LCF, I've tried taking one of the working IS's and editing -- nothing. These are just (custom) listing parameters! All the values remain blank (---) and locked! Why is this happening, and why are our other two schedules working just fine?

Any thoughts?

[Karl Ottenstein]

GS tech support was very helpful and spent quite a bit of time tracking this one down. Here is the code that they found that prevented the editing of the fields:

GS wrote:
The GDL developers were a bit surprised that the code worked in AC 10. Here is the bad code in the zone stamp.

FOR i = 1 to 35
	IF scales = GLOB_SCALE THEN aIndex = i
	found = 1
NEXT i
IF found <> 1 THEN aIndex = 36

It should be replaced with this:

aIndex = 36
FOR i = 1 to 35
	IF scales = GLOB_SCALE THEN
		aIndex = i
	endif
NEXT i

Or this,

FOR i = 1 to 35
	IF scales = GLOB_SCALE THEN
		aIndex = i
		found = 1
	endif
NEXT i
IF found <> 1 THEN aIndex = 36

As you can see, a very common programming error was made in the original code which should have been like the final code fragment to make sure that both assignments happen when the condition is true. The net result is that in the original code, Found was always 1, even if the scale was not matched. aIndex might never be assigned a value, but with found=1, aIndex certainly would never be assigned 36.

The suggested, middle, code is better IMHO. Less complex and no need for the Found variable (which is presumably initialized to 0 somewhere 'above' in the other examples - one should not count on 'default' initialization!).

Why this would cause the fields to not be editable in the schedule isn't obvious to me without studying all of the stamp code. Not mine to post.

Karl

[Laura Yanoviak]

vfrontiers wrote:
Can you post the stamp here?

Sorry -- I guess I should clarify -- this was a purchased Stamp, customized for our needs, so I cannot post the actual Stamp. I have, however, notified its author of the issue and its fix.

[Anonymous]

Thanks to those who did some research on this issue. I took the revised code script and inserted into the super zone gdl script. I worked beautifully. Thanx!!!