On Sun, Feb 24, 2002 at 07:38:46AM -0800, David A. Desrosiers wrote:
> Welcome to the 64k barrier. You need multiple segments, or jumps of
> <32k between them.
Hmm.. that doesn't quite sound right...
> > I'm 99% certain its being caused by my jogdialform.c file somewhere,
>
> How large is that section of code?
Filesize wise, or lines?... jogdialform.c is 6122b, and 168 lines.
I actually had this problem earlier when mucking with viewer.c. I tracked
that problem down to using the Prefs() procedure each time I needed a
setting. Ie, initially I had for a codechunk:
switch (event->data.keyDownchr) {
case vchrJogUp:
if ( Prefs()->jogMode[ JOGDIALS_UP ] != SELECT_NONE && Prefs()->jogdials )
DoSelectTypeAction( Prefs()->jogMode[ JOGDIALS_UP ] );
handled = true;
break;
...
}
and that failed with the same style error message. I altered the code to...
Preferences* prefs = Prefs();
switch (event->data.keyDownchr) {
case vchrJogUp:
if ( prefs->jogMode[ JOGDIALS_UP ] != SELECT_NONE && prefs->jogdials )
DoSelectTypeAction( prefs->jogMode[ JOGDIALS_UP ] );
handled = true;
break;
...
}
Which compiled and worked cleanly. The interesting thing about this though
is that last night I brought over the major changes with the HEAD tree into
my branch, and it was only after that point that things started breaking,
but nothing changed in formjogdial.c ofcourse; and that always compiled
fine asis.
formjogdial.c uses Prefs() 8 times in my code. Is it an acceptable solution
to use the same method described above on this code, or is there another
underlying issue going on?
(Ofcourse, I initially started by using Prefs() in that fashion becuase
everything else was doing it)
I guess I should also confirm that this isn't local on my machine. Does
the same thing happen for anyone else?
Michael, you could probably test this :)
--
Adam McDaniel
Infrastructure Technology Consultant
M-Tech Mercury Information Technology, Inc.
