Re: VARPG - Program organization question

don't fuss over the organization.  Focus instead on the events.

For instance, to work with the code involved with a push button, right click
on the pushbutton and choose "Events" and then click the event you wish to
work with i.e., "Press".

That will take you direcctly to the section of code you care about.

Very neat and very accurate.

--------------------------------------------
Booth Martin
MartinB@Goddard.edu
802-454-8315 x235
--------------------------------------------
-------Original Message-------

From: code400-l@midrange.com
Date: Monday, April 15, 2002 11:49:39 AM
To: CODE400 EMail List (E-mail)
Subject: VARPG - Program organization question

Now that I am working on a second project & it is getting bigger, I was
wondering what the "rule of thumb" some of the more experienced coders are
using for managing/arranging the source code.

As I add a new function, it gets added to the bottom of the program. Then
as changes are made to the program, I end up scrolling through the code
looking for the correct function. What I am contemplating doing is to put
the functions in order by window, part, & event.

This seems to be a logical order but that is why I am asking the question.
Is it or what do you do or what other suggestions might you offer?

I noticed the compiler listing is by part, event, & parent (window) but I
guess I would be more inclined to group by window, part, & event because
that is the way I would think out a program. But then this is only my third
program so who am I to know?

Thanks - Dennis.

Dennis Munro

"I love deadlines. I especially like the whooshing sound they make as they
go flying by." Dilbert's Words Of Wisdom:

Badger Mining Corporation
www.badgerminingcorp.com
dmunro@badgerminingcorp.com
(920) 361-2388

_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.