CompuServe Thread

Animator VBX

6 messages in this thread
#97828From: SteveApr 19, 1994 5:26 PM
To whom this may concern: I am using your custom control vbx to implement animations. Unfortunately, I cannot specify a new animation flic during runtime. VB or your program specifies an invalid format error, despite the fact that the type is flc/fli. I also attempted to run your demo program and received the same error. Is this a problem with the custom control? Adlai Taha Micro Interactive 212-366-1391 76216,3341
#97941From: Brian Rudolph [Adesk]Apr 20, 1994 10:47 AM
Since even the demo program is giving you the same error, I would suspect it to be something in your environment that is causing this. Are there any details or clues you give us about your programming environment that might help us track down what is causing this problem? Have you added any developer kits or programs to supplement the basic Visual basic package? Which version of VB? Were there any problems during the installation of the Player developers Kit? Anyhting else you can tell us? -Brian
#98023From: T. Lee KidwellApr 20, 1994 7:08 PM
Brian, this was one of the problems I mentioned in my previous message which Nick promised to pass to you. I believe the documentation tells you that the Animation Property is not changeable at runtime. I overcame this by using a .AAS script file. However, my problem was with the fact that the DOS scripting allows a pause at the end of the animation. When I tried to take my animations to VB and use VBPLAY I could only stop the animations on the first frame. Could you check on this message for me. It was rather long with a full explanation of the problem. Sorry to butt in but I just had to cease the opportunity.
#98146From: SteveApr 21, 1994 12:39 PM
Dear Brian: I was unable to go through the install program. It would ask if I had vga then it would search for a driver and then it would die. No disk loading and gauge is still up. This is not much of a problem now because I am able to script which is what I need. I am having a couple of other problems. First and foremost, whenever I set the visible property to false the window underneath the flic player causes a flash of whatever color is my my background color is. Is there a way for prevent this? Ideally, I would like the background to be either transparent or just plain history(no longer existing). This would be a great help if you could respond to this. Also I am experiencing some palette flashes when going from a picture box to a flic. <-Don't worry about that one, I still need to do more testing. Thank you -Adlai Taha 76216,3341
#98172From: Brian Rudolph [Adesk]Apr 21, 1994 4:01 PM
<<It would ask if I had vga then it would search for a driver and then it would die. No disk loading and gauge is still up>> Steve, This just makes me think even more strongly what I said a few messages ago, that I do not think you Windows and programming environment are set up properly. PLEASE reinstall the basic setup for your Windows Display, the Autodesk player for window, the MCI driver, and your Visual Basic program. DO NOT install any add ons or developer tolls for VB. Until we strip your environment down to its most basic configuration, we can't start figuring out what is wrong. -Brian
#98317From: Brian Rudolph [Adesk]Apr 22, 1994 11:45 AM
Steve, I just got this information from one of the programmers. I'm not sure this is exacly what you are trying to do, but it might be relevant. —–Fist reply— Hi Brian, The VBX control doesn't respond to the aaNotify events as far as I can tell. I have no idea why a second flic can't be loaded. The example routine can do this just fine. —my response— Thanks for the reply. I was not aware that VBX control does not respond to aaNotify events. Isn't aaNotify in the Programmers Reference manual? Or am I getting C and VB mixed up, where it is available for C and not for VB? -Brian –his 2nd reply— Well, the docs say that AnimFrame accesses the aaNotify call, but I really don't think the vbx has any code to handle it. I suppose I could check it out in the source, but for now I don't have the time. —— I hope this helps. I will continue to explore this issue. -Brian