[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 7.286::atarist

Title:Atari ST, TT, & Falcon
Notice:Please read note 1.0 and its replies before posting!
Moderator:FUNYET::ANDERSON
Created:Mon Apr 04 1988
Last Modified:Tue May 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1433
Total number of notes:10312

173.0. "Using DOWN-ARROW in a FormDo interaction." by PANGLS::BAILEY () Sun Jul 24 1988 16:52

    I have been trying to make a dialogue with 16 editable text fields.
    
    I create the box with a resource editor, and then I do the
    AESForms.FormDialogue(...); AESObjects.ObjectDraw(...);
    AESForms.FormDo(...); thing to animate the dialog.
    
    Everything works fine, except,  the down arrow key, which allows
    the user to move from one text field to the next, allows the cursor
    to disappear beyond the last editable field.
    
    I have seen other programs in which the correct behaviour is exhibited
    (the cursor will not advanced past the last field), but I can't
    for the life of me figure out what is wrong with my situation.
    
    Note that I have gone over the resource tree with a fine tooth comb,
    and can find nothing wrong (it graph box around 16 strings (prompts)
    alternated with 16 Ftext fields).
    
    Is there some trick to this?
    
    Thanks,
       Steph
T.RTitleUserPersonal
Name		DateLines
173.1Is LASTOB set?PRNSYS::LOMICKAJJeff LomickaSun Jul 24 1988 23:3510
Are you using the resource as it comes out of the resource editor, or
are you taking the data and modifying it in any way first?

Did you make sure the last element has the LASTOB flag set in the
ob_flags field?

I don't know of any trick to it, other that the requirement that te_ptext
have @'s in it, and te_ptmplt be X's.  It works for me.  I use it in
TOSHIBA.ACC uploaded today.
173.2Oh yah, LASTOB...PANGLS::BAILEYMon Jul 25 1988 16:448
    > Are you modifying it...
    
    Well, I tried it both ways, but I had forgotten about LASTOB.  I'll
    check that.
    
    Thanks,
      Steph
173.3Maybe I'll just note the problem in TFM.PANGLS::BAILEYTue Jul 26 1988 12:5021
    Well, without changing anything, the 16 element case now works
    correctly (the Atari seems to be suceptable to code rot when one
    is in the process of developing apps.  I reboot mine about four
    times per hour)
    
    But, when I modify the form so that, say, the second element is
    the last (point the root object's TAIL pointer at this element,
    point this object's NEXT pointer at the root element, and set the
    LastObject flag in this object) the cursor still seems to be allowed
    to move down 16 times before it ``bottoms out''.  Where the cursor
    goes after the second object is somewhat helter skelter, but does
    seem to bear some correlation to where the other objects (about
    which FormDo should have no knowledge) are.
    
    I have set a breakpoint immediately before th FormDo call, and examined
    the structure with a debugger, and everything is as I have described.
    
    I'm sure I'm missing something trivial, but I can't find it.
    
    Steph
173.4You're not aloneDECWET::HAMBYTue Jul 26 1988 16:026
    For what it's worth, this problem also plagues me. I'd blamed it
    on my resource editor (the Gem RCS). Even if said software is innocent
    in this case, I loathe it for its random crashes and its incomplete
    functionality...
    
    John
173.5Another, me too, and a bug.PANGLS::BAILEYThu Jul 28 1988 17:5410
    I ran some other programs which do this as well.  (MemFil, for
    example).  I'm really curious about where GEM is getting the info
    about where to stop the arrow.
    
    Have you ever tried typing a TAB while editing?
    
    Another interesting fact is that if a DA loads a resource file,
    GEMDOS loses 40K in the process...  I can't wait for the new ROMs.
    
    Steph