Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login




Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Donate Today!

Do you enjoy these
technical forums?
Donate Today! Click Here

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

KenshinHimura (Programmer)
29 Apr 04 18:14
After a whole mess of testing it seems that in &H1C96 in qb45 is the number stored for the color in the PRINT statement. Could some people test this out for me and see if it works in their version of qb and on their computer? It only works for SCREEN 0 and is a little faster than the COLOR statement. I know this is useless because you can POKE directly to the screen in SCREEN 0 thru &HB800, but its still interesting to now. Some1 should get arounding to documenting the memory segment and each of its functioning of QB. I don't have time right now, but it seems like an interesting project. I guess now I'll try to figure out how it works with other SCREENs. PLZ test it out.... all you got to do is POKE &H1C96, randomvalue and then PRINT someting and see if it changes the color without the COLOR statement. thx
KenshinHimura (Programmer)
29 Apr 04 20:33
Well, I found out that &H1CE9 is the address for SCREENs other than 0 color for the PRINT argument. Well, I don't really see how ne1 (besides me) can use this information, but I don't think it's common knowledge. It did save me though from writing a whole new Print routine with a custom font (man that woulda taken forever). Note: You have to be in Qbasic's default SEGment so use DEF SEG without the argument.
Barok (MIS)
30 Apr 04 23:52
when i want to make my own custom font routine, i just make one that uses my put routine (that clips and masks) to put the text in.  fast and easy, plus switching fonts is a breeze.
Buff1 (Programmer)
6 May 04 23:51
Using Draw affords an easy way to make custom fonts too.
Takes some time to get each character wanted looking right
but ive made several that way and they are surprisingly fast.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Back To Forum

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close