How exactly LCDOUT statement works?

[mpgmike]

This thread illustrates why I use maybe 80% of the PBP commands, but manually work with SFRs for the other 20%. I don't use LCDOUT (and several other commands), as they occasionally don't work with the PIC I'm using, or I can't get them to do what I want. If all else fails, PBP does an excellent job of enabling the programmer to manipulate SFRs manually. I create Subroutines to do what certain PBP commands are supposed to do. In fact, I don't even use ADCIN anymore after it failed on one of the PICs I worked with several years ago (forget which one).

This thread has brought forth what I consider to be valuable questions that lead to knowing what actually goes on in the background. The PBP Commands that I still use (most, actually) are ones that after discovering what they do, I like-endorse-value the PBP approach. Those I have abandoned are ones that I feel I can do an adequate job (perhaps even better for my application) than the PBP approach. Hobbyists appreciate the simplicity of the PBP Commands. Those of us that NEED absolute functionality may decide to manipulate the SFRs instead of using convenient PBP Commands. This thread has been educational.

[CuriousOne]

Well it's about knowledge.
For me it would be great if there were commands which directly work with WS2812, DHT22 and a huge list of other hardware, which is not supported right now....

[Ioannis]

... In fact, I don't even use ADCIN anymore after it failed on one of the PICs I worked with several years ago (forget which one)...

Well in contrast when I fail to use an ADC, I turn to ADCin and works first time! Taking more code space I guess and time...

Well it's about knowledge.
For me it would be great if there were commands which directly work with WS2812, DHT22 and a huge list of other hardware, which is not supported right now....

Then it would be Arduino and not PBP...

Ioannis

[CuriousOne]

lol ok, let's remove LCDOUT, OWIN, ADCIN, SEROUT and others too?
Instead of adding something useful like NEOPIXEL $ADDR,$BRIGHTNESS,$R,$G,$B

[richard]

adding something useful like NEOPIXEL $ADDR,$BRIGHTNESS,$R,$G,$B

all of my posted examples can do that easily, except for brightness as its a function of r g b so would be a totally useless input

http://www.picbasic.co.uk/forum/showthread.php?t=23399
http://www.picbasic.co.uk/forum/showthread.php?t=20973

a neopixel usercommand could be added with a few more lines of code to make the process more explicit
but its trivially easy as is.
very few have shown any interest in this code , very few have even asked a question.

large arrays of neopixels can be resource hungry and will need a midrange chip. a general purpose version is and will
remain a fantasy, the hardware must match the job

[Ioannis]

large arrays of neopixels can be resource hungry and will need a midrange chip

tell me about it... That is why I prefer APA101.

So every job needs its tool. Cannot one size fit all.

Ioannis

[CuriousOne]

But arduino does neopixel with ancient chip with ease?
and also supports brightness? (it is also supported with RGB, you know?)

The libraries and our own addons are of course great, but I'm speaking about centralized support - you just type in, it just works. No forum searching and guesswork.