🚀 go-pugleaf

Ken,

In <8909142033.AA06916@cory.Berkeley.EDU> you write:

>>Ok, I got into WMC's Resource and first typed in 20 spaces, then
>>moved to the first character postion (in front of those 20 spaces)
>>and inserted an @-sign.  When I inserted the @, the spaces
>>were no longer visible (just underbars).
>>
>>I saved the new .rsc and decompiled it to look at the components
>>in textual form.  The @ + 20 spaces were there, though when it
>>decompiled, all of the CNAMEs for my edit fields had been changed
>>to really helpful names like FTXT_27A!
>
>oh, interesting... Odd... Could you still reference the fields by the
>names _you_ specified?  Do you have a Boxtext or what?

No, I couldn't get it reference the fields by the names I specified.
I had to get back into Resource and replace the generic names with
my original names.  I called MWC about it, and they said it would
be placed in the bug report bin.  What ever that means!  :-)

>>>Ok, the @ ensures you start on the left of the field before
>>>the user enters anything (and it's there, trust me), the blanks
>>>give space for the user to enter something!

>>I loaded the .rsc, that I had just built using Resource, into my program
>>and tried to edit the form.  The cursor cursor was at the beginning
>>of the field as you predicted and I could type in 20 characters of text.
>>HOWEVER, the new characters did not replace the underbars but instead
>>merged with them.  So I get R's that look like funny B's and A's that
>>look like sick 8's.  
>
>Sounds like something is funky with flags elsewhere, you've got the
>principle down for creating editable text fields that are default
>to empty -- You might try re-creating the while shape from scratch...
>Sometimes K-Resource (oh, I mean MWC Resource ;-)) gets confused ;-)

Boy, you must be psychic because that is exactly what I did.  I got
out my unused copy of Compute!'s _ST Applications Guide: Programming
in C_ and copied how that guy rolled his own.  I then inserted this
new TEDINFO in place of mine and the thing worked!  Hmmm.  Where were
they different?  It was in te_color and te_thickness.  I dug around a
little deeper and saw that there is a bit (bit 3 {2^3} the MSB of the
high nybble of the low byte) in te_color that is the TRANSPARENCY
flag.  MWC's Resource defaults to transparent and I had never changed
it to OPAQUE. By flipping it in Resource the form now works exactly
as I originally wanted, w/o having to patch the OBJECTs in my code.  

>>>Try it, it should work if you do it _exactly_ like that and don't
>>>worry about not being able to see the @, ok?
>
>>Well, I think I have followed your instructions to the letter (almost
>>literally) and it's almost there, but asthetically unpleasing.  Have
>>I missed something?
>
>Nope, you got it, something somewhere else is messing this up... I can't
>imagine what it could be... ;-} When I get home I'll see what I can come
>up with, so probably more mail later, OK?

Well your hunch was right on the money.  I want to thank you, Steven
Jacobs (saj@chinet.chi.il.us), and Robert de Vries (robert@duttnph.tudelft.nl) 
for all of the help in getting this fixed!  Thanks!!!n

-c
| Chip Roberson                ARPANET:  csrobe@cs.wm.edu           |
| VA Remote Sensing Study                                           |
| Dept of Comp. Sci.                     csrobe@icase.edu           |
| College of William and Mary                                       |
| Williamsburg, VA 23185       UUCP:     ...!uunet!cs.wm.edu!csrobe |

 -=- The Animal-Rights mailing list is now on the air.           -=-
 -=- Send mail to Animal-Rights-Request@cs.odu.edu to subscribe. -=-