On Jun 25, 2004, at 3:16 PM, Dan Shafer wrote:
This app also does no menus other than those contained in the app, for some of the same reasons.
Now, in this app, I elected to do NO "menu stuff." None. Why? Every time I tried messing with menus, Rev would crash. ;-) ALL of my menus are contained within the app, in the form of option buttons, etc. It isn't ideal, but this particular app can stand that without seeming out of the ordinary.
So, that leaves me with menus as a suspect to increased frequency of crashers.
Okee dokee, well then, I wonder what else is so different. As far as plug ins, I have the defaults there, which I don't think I ever use, and I have Chipp's altPlugin bar, with about a half dozen of his plugs "active."
My program makes extensive use of VideoGrabber, Sockets, LibURL, and has roughly 120 controls and 4000+ lines of code in the one main card (and its control objects.) It also uses a slew of resource substacks, and dynamically generates stacks, cards, and text files. It parses incoming socket messages about 4-10 times a second, and updates the status of most of its controls based on the results of that data in addition to creating stacks and cards to store the data, while simultaneously doing FTP uploads and downloads. No menus. ;-)
Would you say that is more, or less, demanding than what you have going on?
I'm just trying to get a sense of what is considered to be complex or demanding. Maybe I just assumed mine was, while it actually isn't.
Or, perhaps we are just tapping into completely different areas of Rev and I've been lucky not to hit on crashing things?
--
Troy
RPSystems, Ltd.
http://www.rpsystems.net
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
