2013-04-23 01:58 PM
2013-04-23 02:20 PM
2013-04-23 02:31 PM
2013-04-23 02:53 PM
2013-04-25 07:33 PM
2013-04-25 09:50 PM
unID = 1 !! X movement HOTSPOT 0, 0, 0, unID, varx, 1 : unID = unID+1 !base HOTSPOT varx, 0, 0, unID, varx, 2 : unID = unID+1 !move HOTSPOT -1, 0, 0, unID, varx, 3 : unID = unID+1 !reference !! Y movement HOTSPOT 0, 0, 0, unID, vary, 1 : unID = unID+1 !base HOTSPOT 0, vary, 0, unID, vary, 2 : unID = unID+1 !move HOTSPOT 0, -1, 0, unID, vary, 3 : unID = unID+1 !reference !! Z movement HOTSPOT 0, 0, 0, unID, varz, 1 : unID = unID+1 !base HOTSPOT 0, 0, varz, unID, varz, 2 : unID = unID+1 !move HOTSPOT 0, 0, -1, unID, varz, 3 : unID = unID+1 !referenceThis will give you three hotspots for the variable "vary", vary", and "varz"
2013-04-27 02:44 PM
luisfmoreira wrote:If you are using the A and B parameters (basic width and depth), then you don't need additional code, they are already inherently stretchable if used as the boundaries of the object.
Now I'm having problems creating hotspots that I can move and that change the A ou B parameter
2013-05-02 10:42 PM
2013-05-10 06:20 PM
2013-05-11 11:36 AM
hotspotIndex=1 hotspot 0, -0.06, 0, hotspotIndex + 1, SOCLD, 1 hotspot SOCLD, -0.06, 0, hotspotIndex + 2, SOCLD, 2 hotspot -1, -0.06, 0, hotspotIndex + 3, SOCLD, 3 hotspotIndex = hotspotIndex + 3 PRISM_ 4, HSOCL, 0.00, 0.00 , 24, SOCLD, 0.00 , 24, SOCLD, ES , 15, 0.00, ES , 15Then, well, I know this is only a sniplet of the code, but to start with the simplest, I suggest you to practice with the standard variables for length (A) width (B) and height (ZZYZX), instead of define your own (SOCLD, ES, HSOCL).