1. "pmake depend" adds PROCEDURE as one of the dependencies. Compile doesn't
work until I take it out. Not a major problem, but was until I figured it out.
2. Esp is complaining that I'm using the genvalue apply messages in both the
.asm and .rdf files. Says it's global in the .asm and local in the .rdf, so
it errors out. What do I have wrong? I have something like
ATTR_GEN_VALUE_STATUS_MSG {MSG_LEFT_MASTER_CHANGE} under the hints of the
genvalues. What do I have wrong? The Esp book isn't very explanatory. It
didn't even say how to declare a message in the class definition! I had to
look through the samples to find out how. I couldn't find how to get the
optr into bx:si either, so again I had to search through samples? Will I
have to be searching through samples a lot if I want to learn Esp? (a lot
being more often than for GOC)
3. Most of the sample apps say they were designed for the PC/GEOS 1.0 API
and that 2.0 is different. But they compile anyway. Is that just something
they never changed when they upgraded the code?
Also, what would I have to do to make the UI in Espire and the rest in GOC ?
I find Espire easier, but I don't see how to do it without at least doing
some of the app in Esp as the uic generates assembly includes. Make a .asm
that just includes the .rdf file and add that to my program?
- -------------------------------------------------------------------
| "You never really understand a person until you consider things |
| from his point of view----until you climb into his skin and |
| walk around in it." |
| -- Atticus Finch, Harper Lee's "To Kill a Mockingbird" |
- -------------------------------------------------------------------
| Edward Di Geronimo Jr. edwdig@bergen.org |
- -------------------------------------------------------------------