wuqiyang312
/
u8g2-copy
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
u8g2-copy/tools/font/build/keywords.pre

110 lines
2.1 KiB
Plaintext
Raw Normal View History

Create keywords.txt Test run for keywords.txt quick test using commands listed in https://github.com/olikraus/u8g2/wiki/u8g2reference included one font in literals for testing. Thought: If font codes where rewriten as u8g2.font.ncenB08.tr then fewer entries would be needed and it might simplify backend code. method: 1. add new line for keyword in proper section 2. after keyword intert literal TAB not spaces. I edited in note pad and copied over. 3. after TAB insert word type (KEYWORD 1, KEYWORD 2, KEYWORD3, LITERAL 1, LITERAL2) more documentation on keyword.txt https://gist.github.com/gschandler/8704468 (template) https://www.arduino.cc/en/Hacking/LibraryTutorial (near the bottom) https://spencer.bliven.us/index.php/2012/01/18/arduino-ide-keywords/ (what are the types)
2017-10-25 02:37:17 +08:00
#######################################
# Syntax Coloring Map For u8g2
#######################################
# Class (KEYWORD1)
#######################################
u8g2 KEYWORD1
#######################################
# Methods and Functions (KEYWORD2)
#######################################
begin KEYWORD2
clear KEYWORD2
clearBuffer KEYWORD2
clearDisplay KEYWORD2
disableUTF8Print KEYWORD2
drawBitmap KEYWORD2
drawBox KEYWORD2
drawCircle KEYWORD2
drawDisc KEYWORD2
drawEllipse KEYWORD2
drawFilledEllipse KEYWORD2
drawFrame KEYWORD2
drawGlyph KEYWORD2
drawHLine KEYWORD2
drawLine KEYWORD2
drawPixel KEYWORD2
drawRBox KEYWORD2
drawRFrame KEYWORD2
drawStr KEYWORD2
drawTriangle KEYWORD2
drawUTF8 KEYWORD2
drawVLine KEYWORD2
drawXBM KEYWORD2
enableUTF8Print KEYWORD2
firstPage KEYWORD2
getAscent KEYWORD2
getDescent KEYWORD2
updated Changelog, release script and keyword marking for Arduino
2019-10-03 17:18:18 +08:00
getDisplayHeight KEYWORD2
getDisplayWidth KEYWORD2
getMaxCharHeight KEYWORD2
getMaxCharWidth KEYWORD2
Create keywords.txt Test run for keywords.txt quick test using commands listed in https://github.com/olikraus/u8g2/wiki/u8g2reference included one font in literals for testing. Thought: If font codes where rewriten as u8g2.font.ncenB08.tr then fewer entries would be needed and it might simplify backend code. method: 1. add new line for keyword in proper section 2. after keyword intert literal TAB not spaces. I edited in note pad and copied over. 3. after TAB insert word type (KEYWORD 1, KEYWORD 2, KEYWORD3, LITERAL 1, LITERAL2) more documentation on keyword.txt https://gist.github.com/gschandler/8704468 (template) https://www.arduino.cc/en/Hacking/LibraryTutorial (near the bottom) https://spencer.bliven.us/index.php/2012/01/18/arduino-ide-keywords/ (what are the types)
2017-10-25 02:37:17 +08:00
getMenuEvent KEYWORD2
getStrWidth KEYWORD2
getUTF8Width KEYWORD2
home KEYWORD2
initDisplay KEYWORD2
nextPage KEYWORD2
print KEYWORD2
sendBuffer KEYWORD2
setAutoPageClear KEYWORD2
setBitmapMode KEYWORD2
updated Changelog, release script and keyword marking for Arduino
2019-10-03 17:18:18 +08:00
setBusClock KEYWORD2
setClipWindow KEYWORD2
Create keywords.txt Test run for keywords.txt quick test using commands listed in https://github.com/olikraus/u8g2/wiki/u8g2reference included one font in literals for testing. Thought: If font codes where rewriten as u8g2.font.ncenB08.tr then fewer entries would be needed and it might simplify backend code. method: 1. add new line for keyword in proper section 2. after keyword intert literal TAB not spaces. I edited in note pad and copied over. 3. after TAB insert word type (KEYWORD 1, KEYWORD 2, KEYWORD3, LITERAL 1, LITERAL2) more documentation on keyword.txt https://gist.github.com/gschandler/8704468 (template) https://www.arduino.cc/en/Hacking/LibraryTutorial (near the bottom) https://spencer.bliven.us/index.php/2012/01/18/arduino-ide-keywords/ (what are the types)
2017-10-25 02:37:17 +08:00
setContrast KEYWORD2
setCursor KEYWORD2
setDisplayRotation KEYWORD2
setDrawColor KEYWORD2
setFlipMode KEYWORD2
setFont KEYWORD2
setFontDirection KEYWORD2
setFontMode KEYWORD2
setFontPosBaseline KEYWORD2
setFontPosBottom KEYWORD2
setFontPosTop KEYWORD2
setFontPosCenter KEYWORD2
setFontRefHeightAll KEYWORD2
setFontRefHeightExtendedText KEYWORD2
setFontRefHeightText KEYWORD2
setI2CAddress KEYWORD2
updated Changelog, release script and keyword marking for Arduino
2019-10-03 17:18:18 +08:00
setMaxClipWindow KEYWORD2
Create keywords.txt Test run for keywords.txt quick test using commands listed in https://github.com/olikraus/u8g2/wiki/u8g2reference included one font in literals for testing. Thought: If font codes where rewriten as u8g2.font.ncenB08.tr then fewer entries would be needed and it might simplify backend code. method: 1. add new line for keyword in proper section 2. after keyword intert literal TAB not spaces. I edited in note pad and copied over. 3. after TAB insert word type (KEYWORD 1, KEYWORD 2, KEYWORD3, LITERAL 1, LITERAL2) more documentation on keyword.txt https://gist.github.com/gschandler/8704468 (template) https://www.arduino.cc/en/Hacking/LibraryTutorial (near the bottom) https://spencer.bliven.us/index.php/2012/01/18/arduino-ide-keywords/ (what are the types)
2017-10-25 02:37:17 +08:00
setPowerSave KEYWORD2
updated Changelog, release script and keyword marking for Arduino
2019-10-03 17:18:18 +08:00
updateDisplay KEYWORD2
updateDisplayArea KEYWORD2
writeBufferPBM KEYWORD2
writeBufferXBM KEYWORD2
writeBufferPBM2 KEYWORD2
writeBufferXBM2 KEYWORD2
Create keywords.txt Test run for keywords.txt quick test using commands listed in https://github.com/olikraus/u8g2/wiki/u8g2reference included one font in literals for testing. Thought: If font codes where rewriten as u8g2.font.ncenB08.tr then fewer entries would be needed and it might simplify backend code. method: 1. add new line for keyword in proper section 2. after keyword intert literal TAB not spaces. I edited in note pad and copied over. 3. after TAB insert word type (KEYWORD 1, KEYWORD 2, KEYWORD3, LITERAL 1, LITERAL2) more documentation on keyword.txt https://gist.github.com/gschandler/8704468 (template) https://www.arduino.cc/en/Hacking/LibraryTutorial (near the bottom) https://spencer.bliven.us/index.php/2012/01/18/arduino-ide-keywords/ (what are the types)
2017-10-25 02:37:17 +08:00
userInterfaceInputValue KEYWORD2
userInterfaceMessage KEYWORD2
userInterfaceSelectionList KEYWORD2
updated Changelog, release script and keyword marking for Arduino
2019-10-03 17:18:18 +08:00
getBufferSize KEYWORD2
setBufferPtr KEYWORD2
getBufferPtr KEYWORD2
getBufferTileHeight KEYWORD2
getBufferTileWidth KEYWORD2
getBufferCurrTileRow KEYWORD2
setBufferCurrTileRow KEYWORD2
Create keywords.txt Test run for keywords.txt quick test using commands listed in https://github.com/olikraus/u8g2/wiki/u8g2reference included one font in literals for testing. Thought: If font codes where rewriten as u8g2.font.ncenB08.tr then fewer entries would be needed and it might simplify backend code. method: 1. add new line for keyword in proper section 2. after keyword intert literal TAB not spaces. I edited in note pad and copied over. 3. after TAB insert word type (KEYWORD 1, KEYWORD 2, KEYWORD3, LITERAL 1, LITERAL2) more documentation on keyword.txt https://gist.github.com/gschandler/8704468 (template) https://www.arduino.cc/en/Hacking/LibraryTutorial (near the bottom) https://spencer.bliven.us/index.php/2012/01/18/arduino-ide-keywords/ (what are the types)
2017-10-25 02:37:17 +08:00
#######################################
# Constants (LITERAL1)
#######################################