Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1,743 Excellent

1 Follower

About senior_falcon

  • Rank
  • Birthday 10/14/1951

Profile Information

  • Gender
  • Location
    Lansing, NY, USA

Recent Profile Visitors

10,077 profile views
  1. Please define a "beautiful function plotter"
  2. The program was done using The Missing Link, not XB256. Labeling is not a problem in TML. If you download TML and run TMLDEMO you would see that text can be displayed anywhere on the screen with pixel accuracy.
  3. 10 CALL LINK("LINE",96,1,96,240):: CALL LINK("LINE",1,120,192,120):: FOR C=-5 TO 5 STEP .04 :: CALL LINK("PIXEL",96-SIN(C)*30,120+C*25):: NEXT C 20 GOTO 20 I will leave it to someone else to put in the tick marks and numbers.
  4. Have you downloaded The Missing Link and looked at the demo program? That would give you a good idea of what can be accomplished. This challenge would take one or two lines using TML. You have expressed an interest in the TI99/4a. Your challenge would be a perfect opportunity to get your hands on the keyboard and actually learn by doing. There are lots of people here who could help guide you when you go astray.
  5. In The Missing Link text does not have to align with the 24x32 grid. If you wanted Hello World! at r153 and c121 you would use CALL LINK("PRINT",153,121,"Hello World!) No problem getting the axes and the characters aligned. Suppose you wanted to use a 5x7 font giving a screen of 48 rows. Like Prego spaghetti sauce, "It's in there."
  6. XB256 is no better at this than any other normal XB. The Missing Link can do it because it gives a full bit mapped screen. Download The Missing Link and run the demo program. (TMLDEMO) In Graphics you will see a sin, cos, tan plot with labelling. There is no mystery in this; all the information you need is in my earlier post.
  7. The Cruz is a nice car with good fuel economy too. http://www.car-part.com/ With this site (or similar) you can search for your door. They seem to go in the $100-200 range. A fellow whose nom-de-net is Richpin has excellent videos on how to fix Saturn S cars.
  8. Actually, you have the same 24K of room for the XB program. You do have considerably less room for the stack in the VDP which is where strings are kept and (as I remember) subprogram names. There is a section in the manual on how to conserve string space
  9. Mine is a 1997 SW2. Sadly the rust from the road salt used around here is really chewing up the steel underneath the car. It has 1 or maybe 2 years left before it shuffles off this mortal coil. Why don't you drive yours?
  10. This is trivial to do in The Missing Link. CALL LINK("PIXEL",row,column[,foreground-color,background-color]) This routine places a pixel on the screen. Including the optional color values will simultaneously change the penhue. Things to remember: row 1 is the topmost row and column 1 is the left most column. Trig functions on the TI are in radians, not degrees. I have too many things going on right now. Why don't you try writing this?
  11. Since you put it that way, now I've gotta give Cortex BASIC a try. I've always wanted a Ferrari. In red, of course. Not useful for picking up plywood at the lumberyard, but that's what my old Saturn station wagon is for.
  12. That is a common misconception. Actually, XB doesn't care where the assembly routines are located. It can run them just fine when they are in the 24K high memory. There is a utility in TML called HMLOADER that will embed assembly routines in high memory and you can then add an XB program to the embedded routines. So you can fill up the 8K from >2000 to >3FFF with assembly routines (or use TML or XB256) and add more routines to the high memory. The compiler runs completely from high memory. By the way, the apesoft routines stink compared to the missing link. Don't take my word for it-compare them yourself.
  13. I just had a thought! Why not do it this way: XB: Write a program test it on spot, fix it on the spot. COMPILED XB: Write Text, compile it, test it, go back and fix Text, compile it, test it. Write a program (in XB) test it on spot (in XB), fix it on the spot(in XB). Iterate until happy with the program just like you would do in XB. Only when the XB program is debugged and complete would you compile it. (Realistically you would probably have to do some adjustment to timings which means compiling a couple of times) Way longer to write, debug and test. Just a tiny bit of added time when you do the compilation at the end. (Actually, this is described in the manual, and so is not a new thought.)
  14. "In computer science, the term threaded code refers to a programming technique where the code has a form that essentially consists entirely of calls to subroutines. It is often, but not only, found in compiler implementations that generate code in that form and/or are implemented in that form themselves. The code may be processed by an interpreter, or may simply be a sequence of machine code call instructions. " The XB compiler does not generate assembly code. Instead, it converts the BASIC program into DATA statements. For example: 10 CALL HCHAR(ROW,COL,42,32) 20 CALL VCHAR(ROW,COL,65,24) compiles to: L10 DATA HCHAR,NV1,NV2,NC1,NC2 L20 DATA VCHAR,NV1,NV2,NC3,NC4 When running, the interpreter retrieves the address of HCHAR, goes there, then retrieves the variables and constants and puts them on the screen. The pointer then advances to the next data statement, retrieves VCHAR, goes there, retrieves the 4 variables and puts them on the screen. And so on.
  • Create New...