' User code that needs to be executed repeatedly goes here or after Check_TP() routine call. While TRUE ' main program endless loop section Start_TP() ' V-TFT generated routine call to initialize HW and V-TFT screen(s) and objects ' User code here gets executed one time only ' Users code can go any where in this module Program pic32mmb_v370_event_counter_example_main ' Tutorial comments done by Robert Townsley (MegaHurts) 2013 ' pic32mmb_v370_event_counter_example.vtft Without more information from you on what exactly you are trying to do with any HW, that is the best I can suggest for now. You MUST start there first and get to know and understand the PICs operations and possible connectivity usages before designing the To the V-TFT project after you create the GUI you want with the components V-TFT has available first.Īll of the information on programming a PIC to control its HW and ports I/O operations is in the PICs datasheet(s) and compiler manuals. It ,or any such, in V-TFT or the compiler to see how the example implements what you are wanting to do also.īe aware, V-TFT does not have the functions or components for any HW other than TFTs and Touch Panels.Īll code for configuring, reading, writing and controlling a PICs internal modules and ports has to be done in a compiler and added It does use the TFT touch panel when running on a device to navigate through the different screens and controls. You can load the source V-TFT project in to V-TFT and see how external buttons are handled as inputs in V-TFT and use its code in your own project. There is a example project that WorkStation users can use to test every button and LED on every port for whichever MMB is inserted in the MMB socket. I can suggest that you get (at MikroE's Libstock website), and look over the examples for the MikroMedia WorkStation V7 development system. Also the available examples + the forum here. Sorry but at this time, there is only the help file for V-TFT users.