| |
PAL
Registered: Mar 2009 Posts: 292 |
want to code
OK dudes... I need to start coding. I am in the need to get up and running... I am a fool and an idiot but I know a lot about the c64 and I know how to but not in code. I need someone who can guide me to start to be a coder, that said it is not like I want to be feed with links... I want to start coding with you as a guide and my mentor!
My dream: is there someone who can put aside one hour a day or second day with me and that know how to make me understand the basics so that I can expand on my own? I know nothing in commands and such as of start we can assume.
I know it might sound stupid but are there anyone out there who could do this? with me?
I can pay back with logos, graphics, part ideas and such...
pal of offence |
|
... 81 posts hidden. Click here to view all posts.... |
| |
PAL
Registered: Mar 2009 Posts: 292 |
I am going into coding and I just wonder about something? It is bugging me much.
The default values for d022, d023 and d024 are initialised with 1,2,3 - why not just set them to 0 or all equal? why is it not set to 0 ?
|
| |
chatGPZ
Registered: Dec 2001 Posts: 11386 |
that is hard to say really. my pet theory is: when developing the c64, it allowed for quick testing with a minimum set of pokes. there is no other good reason for the weird defaults, imho :) |
| |
algorithm
Registered: May 2002 Posts: 705 |
Its the same for other io locations such as d027 onwards etc. Just the way they are initialised I guess. Its not stopping you from changing them |
| |
chatGPZ
Registered: Dec 2001 Posts: 11386 |
"Just the way they are initialised I guess."
however, the values come from a table in ROM - making most of it 0 (or any other more sane value) would have been no problem. |
| |
algorithm
Registered: May 2002 Posts: 705 |
Groepaz. That is still classed as initialisation :-) |
| |
PAL
Registered: Mar 2009 Posts: 292 |
I just got back to this in my mind when I try to code here... hmm... made a vsp today, thanx cruizer for the code... trying to grasp it all... maaaan it is hard to start coding at the age of 39!! |
| |
algorithm
Registered: May 2002 Posts: 705 |
Noooo. Vsp is evil. Even with the workarounds to skip corrupted areas and to to retransfer bytes back to damaged areas. Although in some cases it can pay off |
| |
chatGPZ
Registered: Dec 2001 Posts: 11386 |
Quote:Vsp is evil
more or less evil than screeching noise? =)
i agree though that a beginner should first learn how to scroll the "normal" way. and certainly he shouldnt use VSP unless understanding the implications *exactly* =P |
| |
algorithm
Registered: May 2002 Posts: 705 |
The implications of vsp are severe and in my opinion vsp should not be used at all unless using the methods of skipping and recovering corrupted bytes in x7 and xf areas. Unless you are scrolling full screen bitmaps fast. Its easy enough to just manually copy shifted gfx to buffer. One good idea as what may have been mentioned before is to have a check at the beginning of a demo on whether there is thst issue with corruption and display warning and alternate methods |
| |
algorithm
Registered: May 2002 Posts: 705 |
"Screetching" noise never crashes :-) |
Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 - Next |