Needed: basic wisdom concerning the use of VGA

Comments

• Erik Friesen Posts: 1,071

  2009-03-16 21:55 edited 2009-03-16 21:55

  You can use vga_text exactly the same way you use tv_text. If you look at the propeller demo board and the way its basepin is used you should have little trouble.
• MagIO2 Posts: 2,243

  2009-03-16 22:07 edited 2009-03-16 22:07

  In the base directory of the propeller tool you find the VGA_TEXT.spin. If you click that and tick the summary radio-button in PT, you only see the functions. All starting with pub can be used. So, str prints a string, hex prints a hex-number. The parameter names give you an hint what's expected in the parameter. Only one which is not self-explaining is the out function.
  Set the cursor to the out-function and click Full Source radio button again. Here the comment gives you a list of special characters.
  
  In the library-folder you find a _demo for each Object which gives you an idea on how to use the stuff.
• Kye Posts: 2,200

  2009-03-16 22:31 edited 2009-03-16 22:31

  Test mine out, it's fully commented and works as you would think it would.
  
  http://forums.parallax.com/forums/default.aspx?f=25&m=335776
  
  You can find it in that tread, just scroll down a few post.
  
  ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
  Nyamekye,
• Mike Green Posts: 23,101

  2009-03-16 22:39 edited 2009-03-16 22:39

  The tv_text driver and the vga_text driver were written to be mostly interchangable. FemtoBasic uses a modified version of both of them to provide "drop-in" equivalence for everything but changing the display colors (since that's different between the two devices).
• ElectricAye Posts: 4,561

  2009-03-17 01:19 edited 2009-03-17 01:19

  Mike Green said...
  The tv_text driver and the vga_text driver were written to be mostly interchangable....

  
  Thanks, Mike, that provides a starting point. And to Erik and MagIO2, too.
  
  To Kye, I will try to have a look at what you've done. The idea that code is offered WITH comments is such a rare blessing. I'm a total non-EE noobie who struggles moronically with every iota of code and components that I add onto my Propeller. Generally speaking, I go through a 3 step process when wanting to put new features into my Propeller system. First, I go nuts because the OBEX code is usually so stripped down, I can't make any sense of it. My blood pressure shoots through the roof and I crash into a dark, brooding depression. Second, after being told that the OBEX code should be intuitively obvious to the most casual of observers, I have a total nervous breakdown, get insanely drunk, and drive my car over a cliff after eating a bottle of sleeping pills and drinking a gallon of chlorox. Days later, I awake in the hospital to find that the OBEX code isn't that hard to understand after all. The clouds clear, the body cast comes off, and somehow, by some miracle, I figure out what people are trying to tell me and eventually get the thing to work.
  
  I tell you, being a Mech E in a world of EE's, it's tough.