MAXScript Rollout Handler Exception:
– Unknown property: “clear” in dotNetControl:dnc_jobsToDependOn:(null) <<
Somewhere around here:
on dn_tabs Selected itm do
(
if LastSubRollout != (itm.TabPageIndex+1) do --do not update if the same tab clicked twice
(
for subroll in SMTD_Rollouts[LastSubRollout][2] do
removeSubRollout sub_SubRollout subroll
for subroll in SMTD_Rollouts[LastSubRollout = itm.TabPageIndex+1][2] do
addSubRollout sub_SubRollout subroll
)
)--end tabs clicked
Not sure what the problem was, doesn’t seem replicable…
Could be something to do with this, clicking the tabs quickly can make problems like this…
D
Going a bit click happy and you can cause a system exception…
And again… something weird like this…
MAXScript Rollout Handler Exception:
– Unknown property: “GridLines” in dotNetControl:lv_limitGroups:(null) <<
MAXScript Rollout Handler Exception:
– Unknown property: “GridLines” in dotNetControl:lv_limitGroups:(null) <<
on dn_tabs Selected itm do
(
if LastSubRollout != (itm.TabPageIndex+1) do --do not update if the same tab clicked twice
(
for subroll in SMTD_Rollouts[LastSubRollout][2] do
removeSubRollout sub_SubRollout subroll
for subroll in SMTD_Rollouts[LastSubRollout = itm.TabPageIndex+1][2] do
addSubRollout sub_SubRollout subroll -------------------------------------------------Stops on this line…
)
)–end tabs clicked
So I’m guessing this is a long-term Maxscript/Deadline issue,
I’m just noticing it more, because of the loading lag with the Tiles Tab, If you click another tab before anything other than the “Tile & Region Rendering Options” rollout has loaded, you’ll get a “3ds Max Region Rendering” Tab added to the subrollout.
