Hi Darrel
Can you please make Vertical_LCDBar.INC like that Horizontal_LCDBar.INC.
Thanks in advance
Hi Darrel
Can you please make Vertical_LCDBar.INC like that Horizontal_LCDBar.INC.
Thanks in advance
Like Alain said way up there.
Due to the spaces between the characters landing on an Odd number, vertical bargraphs on LCD displays don't work very well.
Bummer!
<br>
DT
Hi, Darrel
Could you explain those lines to me :
ASM
lines = 0x10000001 ; Define the Styles
boxed = 0x10000002
blocks = 0x10000003
ENDASM
(From LCD_Bar.inc ) ...
My MPLAB 7.30 seems not to understand it ( comes in red ) ... nor me !!!
Alain
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
Hi Alain,
Those just assign some unique ID's to the words lines, boxed and blocks.
I used numbers outside the 16-bit range of PBP just to minimize confusion for myself. Then when PBP uses the number, all it sees is 1, 2 or 3.
I haven't bothered downloading the latest MPLAB so I hadn't seen any problem yet. But it should be ok to just make them 1, 2 and 3
<br>Code:ASM lines = 1 ; Define the Styles boxed = 2 blocks = 3 ENDASM
DT
Hi Acetronics
I had the same problem, when you use the macro, be careful about the letters upper and lower case thingy, I mean Blocks and blocks are different when you use MPASM. Darrel wrote blocks in LCDbar_INC file in the difintions, so you have to use blocks, not Blocks in the macro, the same applies for lines and boxed. This worked fine for me.
For example:
In order to change to Blocks, Lines, and Boxed. Instead of block, lines, and boxed, you have to change the following in LCDBar_INC file:Code:' In LCDbar_INC file you will find the following definitions that darrel wrote: ASM lines = 0x10000001 ; Define the Styles boxed = 0x10000002 blocks = 0x10000003 ENDASM ' No need to change them nay way... In your code, you will use this macro: ; BARgraph Value, Row, Col, Width, Range, Style @ BARgraph _VOL_L, 2, 0, 20, 255, Blocks ' Doesn't work ; BARgraph Value, Row, Col, Width, Range, Style @ BARgraph _VOL_L, 2, 0, 20, 255, blocks ' Works fine
And this too:Code:ASM Lines = 0x10000001 ; Define the Styles Boxed = 0x10000002 Blocks = 0x10000003 ENDASM
After that you can use Blocks, Lines, and Boxed in your code macro.Code:if ((Style >= Lines) & (Style <= Blocks)) ; Is Style a valid constant ? MOVE?CB Style, _BAR_style else ; NO, treat it like a variable MOVE?BB Style, _BAR_style endif
Last edited by crematory; - 14th January 2006 at 17:38.
Seems like a lot of work to rewrite a program to use a different Case, when you can just turn off case sensitivity for MPASM, and use any case.
For MicroCode Studio Plus:From View | Picbasic Options... | Assembler Tab and Options tabThe Microchip MPASM checkbox must be checked to see the Case option.
uncheck the "Case sensitive" Checkbox
Press OK
For other editors, or dos:Add -c to the MPASM command line.<br>
DT
Hi darrel
I could have said that, as a matter of fact, being careful about letter cases while writing a code, prevented me of throwing that note about "uncheck the Case sensitive Checkbox", thats all darrel,
Bookmarks