Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
wrong characters in XP graphics.
#11
Hi, Ralph - F8! Right! How could I forget that? Breakpoint, variables tracking, etc, I recalled, but F8 was the one I forgot.
But there is another problem. Since I messed up with the program when I started trying to structure it, I killed some subs, so the shift-F5 and F8 do not even start the program because bc71 alerts that there are inexistent subs that are called somewhere by the program. Search is no showing the subs, that is, they are in some lost module. What a mess.  To Rem those calls may be the only temporary solution. What a mess. 
I 've realized that screen and other commands work with parameters that are changed within the program.

Anyway, I know already that the monitor spec does not have anything to do with the problem. The monitor works fine with a toshiba notebook running updated xp sp2. So the XP update issue is not the cause too.
I've noticed that the text is coming in special characters (signs) instead of the standard alphabet. Same number of characters. However, in a exclusively text window of my program, the characters come out ok. Only the graphics windows puts its text in special symbols instead of normal alphabetical wording. Therefore, it seems that it cannot be another software in the background too.
Does this makes you suspect of anything? 

Reply
#12
Perhaps Mac can better answer your question, but, here's my thought.  If normal, alphabetical letters and digits are being shown as strange symbols, it may be that the normal characters have had a constant added to them.  How?  No idea.  But, it might be interesting to have a list of the characters that are appearing; someone may be able to de-encrypt them!  Well, it's just a thought, but, who knows?

As to you having altered your original code, etc., are you saying that you changed the original code, without using a copy?  Wow!  But, if you still have the original code somewhere (look for it ardentlay!), then, all is not lost.

Ralph, using QuickBASIC 4.5 and Windows XP Home Edition and Service Pack 2, with HP LaserJet 4L printer.
Reply
#13
This may just be my personal preference, but when working in qbasic, I write and run in a vmware or virutal pc virtual machine of dos 6.22. I'm sure DosBox emulates properly, but if not, someone please write me back. If I ever distribute any of my qb programs, I plan of including  a copy of DosBox, ala the re-release of Wolfenstein 3d. BTW I'm running both Vista and XP.
-s.davis
Reply
#14
Jacobb:

When the code for a program becomes unintelligible, or when some of the code is missing, and we struggle for a while and decide it's just not possible, about the only sane and reasonable solution is to start from scratch, that is, rewrite the whole thing!  And, this time, begin by writing up a good desciption of the proyect in a good word processor, saving the file with the intended program's name. 

The second step is to do some general coding that works, and save it with the desciptor, say, filenm00.bas, saved as text.  I also like to preface my code with a brief description of the program's use, as well as a numbered single-line title for each of the intended steps for the program, which I modify as I progress with the code, doing an update on each finished "version". 

For the next step, call up filenm00.bas, save it immediately as filenm01, and start working on it.  Write the next bits of code and run it, making sure it works...if not, fix it...; if you cannot, then, bring up the last, working copy (filenm00 will be the first), save it immediately as the next number in line (filenm01, for the case in point), and continue in this manner, ending up with as many "versions" as you need. 

Now, save all the "versions" to some conveniently located folder named, say, filenm,  copy the last and greatest one to your qb folder (directory), and proceed to compile it. 

Oh, I almost forgot!  DO USE GOOD, EXPLANATORY REMARKS for each new paragraph of code, either just before writing it, or just after, so that, when you have to go back to your code next month or next year, you will have good reminders of what the code is supposed to do.  These remarks will someday be worth more than one can believe!!!

And, good luck!
Ralph, using QuickBASIC 4.5 and Windows XP Home Edition and Service Pack 2, with HP LaserJet 4L printer.
Reply
#15
it might be adding 127 or 128 to the character code e.g.

print chr$(65)

prints a capital A but it might be printing character 192 or character 193 because of a screen driver, both of which are special characters. 
WHILE RPG$ <> "complete" : make up silly excuses :WEND
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)