I have problems with the visual maxscript that I have begun using more frequently lately.
Normally I always control all the states of the buttons with variables. MaxScript destroyes these variables however. Is there a way around this that is smooth?
Example
Yehaa_state=true
checkbutton chbYeeeha “Yeeeha!” checked:Yeeeha_state
If I run edit rollout with visual maxscript, it will now look like this
checkbutton “Yeeeha!” checked:true
One way that would fix this is to call a special funtion either when you create the rollout, or right afterwards, and in this function manually setting all the values.
so
fn_Init=(
chbYeeha.checked=Yehaa_state
)
So perhaps putting this in the rollout on open event?
Or is there a way you can make visual maxscript keep your variables?
,
Andreas
Hi Andreas,
VMS is a bit outdated, and I hear that it is no longer going to be developed so I suggest using it to get use to what the code should look like, and then just write it yourself. It hasn’t changed since it’s conception back in MAX3 or there abouts and it’s unlikely to change now.
Josh.
Hmm, this is way too common in max. They have a great idea, develop it to 50% and then leave it.
I have found ok ways to work with visual maxscript. What I do is I create an event for the rollout
on rol_moved open do
(
–set all properties on the objects.
)
This works without maxscript destroying.
/Andreas
The source code for VMS has shipped with the Max7 SDK, so theoreticly any bugs in there can now be squashed… It was written with MFC, as far as I know.
Chris J.