RE: Herc in Microwin
hi As discussed last week on this list, vert_line is mislabeled, it should be horz_line (exactly how *did* that happen, Bjorn?? ;-) greg, the list you are talking about is [EMAIL PROTECTED] right? : I have not started the vertline func yet, but as I say the hline is nearly : ready. No need for an optimized vertline, there's nothing that can be done to the existing code to speed it up... Thank god, because I could not think of anything!! No - scr_herc.c was written by me based on Jacob's code. (thanks Jacob) I assume you're starting with scr_herc.c, the working hercules screen driver. Yep thats the file I am adding to. tom __ Get Your Private, Free Email at http://www.hotmail.com
RE: Herc in Microwin
: Bjorn Eriksson's code : void vert_line(US x1, US x2, US y, const BYTE color) : : This confuses me, why does a vert_line func have 2 "x" vals??? Or is a : general typo, wouldnt that be a horizontal line, like you say?? : As discussed last week on this list, vert_line is mislabeled, it should be horz_line (exactly how *did* that happen, Bjorn?? ;-) : I have not started the vertline func yet, but as I say the hline is nearly : ready. No need for an optimized vertline, there's nothing that can be done to the existing code to speed it up... : : This may seem like a silly question, please dont get mad, but, what do you : mean "the code you're running now is based on Jacob's code", baring in mind : I have never done a programming task in a group. Is it that I use the : #defines and stuff he has? : No - scr_herc.c was written by me based on Jacob's code. (thanks Jacob) I assume you're starting with scr_herc.c, the working hercules screen driver. Greg
RE: Herc in Microwin
hi Greg:- Good luck. Remember, the code you're running now is based on Jacob's code, and we want to add the horizontal byte-filling code that Bjorn sent us. Bjorn Eriksson's code void vert_line(US x1, US x2, US y, const BYTE color) This confuses me, why does a vert_line func have 2 "x" vals??? Or is a general typo, wouldnt that be a horizontal line, like you say?? I have not started the vertline func yet, but as I say the hline is nearly ready. This may seem like a silly question, please dont get mad, but, what do you mean "the code you're running now is based on Jacob's code", baring in mind I have never done a programming task in a group. Is it that I use the #defines and stuff he has? Greg tom __ Get Your Private, Free Email at http://www.hotmail.com
Re: Herc in Microwin
Hi I have some examples in asm in a book. Whats the book, sounds great, ISBN??? I will try to remember mailing you what info I have when I get home later tonight. (GMT + 1) GREAT!!! Get Your Private, Free Email at http://www.hotmail.com (Not so private... :-) yes...hehe... I am still...(deap breath)...configuring sendmail/fetchmail/procmail/mailreader for my pop account! I have only been using linux for a year, and 6 months of that I did not use it!! Kind regards, Jakob Eriksson Thanks Thomas __ Get Your Private, Free Email at http://www.hotmail.com
Herc in Microwin
Hi all I have now got the bones of a optimzed hline for a herc card done. 1. I have to get rid of those nasty bugs. 2. How do I write to bytes to memory correctly. The origanal drawpixel uses a pixel value c as well as the x and y cords. And therefor the hline uses this c as well. It does:- if(c) ORBYTE_FP(dst, mask); else ANDBYTE_FP(dst, ~mask); What is the pixelvaue "c" for? Who gave greg that code? Greg? 3.um...I am quite pleased I got this far, because I am new to all this. From Thomas Stewart :-) at [EMAIL PROTECTED] __ Get Your Private, Free Email at http://www.hotmail.com
RE: Herc in Microwin
: 2. How do I write to bytes to memory correctly. The origanal drawpixel uses : a pixel value c as well as the x and y cords. And therefor the hline uses : this c as well. : : It does:- : if(c) : ORBYTE_FP(dst, mask); : else ANDBYTE_FP(dst, ~mask); : : What is the pixelvaue "c" for? Who gave greg that code? Greg? In the MicroWindows/Nano engine, there are color values (COLORVAL) and pixel values (PIXELVAL). COLORVALs are now always 32 bits, and hold the RGB color we're looking to see. After translation by the palette manager section of devdraw.c, the color value is converted into a device-dependent PIXELVAL that is essentially an index into the video card's palette, *or* the hardware RGB value, if the card is truecolor. Translated, for you the pixelval is either 0 or 1 (black or white), since you're running a monochrome screen. So, if c == 1, then you OR a bit into screen ram, else you AND out (set to 0) a bit. Good luck. Remember, the code you're running now is based on Jacob's code, and we want to add the horizontal byte-filling code that Bjorn sent us. Greg :
