 | | Re: tweaking around dlcd_show( )
|
| (...) Ooops! I obviously wasn't looking at it properly last night (only browsing through the zip file). As 'dlcd_show' is defined as a macro that takes one parameter, but uses it twice to each of BIT_OF and BYTE_OF, which in turn both take 2 (...) (23 years ago, 26-Aug-01, to lugnet.robotics.rcx.legos)
| | | | | Re: tweaking around dlcd_show( )
|
| (...) Nope - bit_set(0xef46,0x4) will work, but not dlcd_show(0xef46,0x4), as it needs only 1 parameter. (...) Choosing the types of the struct elements is the problem - these are passed to the h8's bset instruction. First, I tried void* & char, but (...) (23 years ago, 27-Aug-01, to lugnet.robotics.rcx.legos)
| | | | | Re: tweaking around dlcd_show( )
|
| (...) Since writing this, I have set up a LegOs build environment, so had a play with it. It doesn't seem very useful the way it is written. See my bit about it below. (...) I had a bit of a go doing this as well, and since I didn't know what the (...) (23 years ago, 27-Aug-01, to lugnet.robotics.rcx.legos)
| | | | | Re: tweaking around dlcd_show( )
|
| (...) LCD_4_BOTL (...) I agree it's a bit bodgy. The one advantage is you only need to pass a single #define when calling it directly (OK not a huge advantage, but if you look at the values in the #defines, you'll see why it was done that way). But (...) (23 years ago, 27-Aug-01, to lugnet.robotics.rcx.legos)
| |
