In MPLABX go to the menu: Tools->Options->Keymap >From there you can set up net beans shortcuts to you hearts content. However, in almost any given IDE the F5, F6, F7, F8, F9 keys are usually mapped to various build/run/debug functions for convenience. It seems F5 and F6 do something in MPLABX but I can't test it. Also in the key mapping tab it shows alt and shift being used in conjunction with some F key functions as well. Anyways, you can look at all of that and change it to make it work for you in the key mapping tab. Good luck! Jason White On Sun, May 4, 2014 at 3:59 PM, Josh Koffman wrote: > Stop the presses!!! > > I am just dumb, and when copying my comment header over to the new > file, I missed a closing slash. So yeah, the compiler wasn't > processing anything in that file. > > I'm sorry about the wasted bandwidth. > > As an aside, does anyone know of a keyboard shortcut to "Build All" in > MPLABX on OSX? I couldn't find something that worked in the Netbeans > reference. > > Thanks! > > Josh > -- > A common mistake that people make when trying to design something > completely foolproof is to underestimate the ingenuity of complete > fools. > -Douglas Adams > > On Sun, May 4, 2014 at 3:53 PM, Josh Koffman wrote: >> Hi all, >> >> I had a few minutes, so I decided to start playing a bit in C again. >> >> I am taking the program I wrote previously, and trying to break it up >> into smaller files. For example, I'm trying to get all the #defines >> that I do to alias to hardware pins and place them in an external >> header file. I want to do this so I can #include it at the top of all >> the other files in my project, so the constant names are universal >> across the project. >> >> So, I created a .h file, and cut and pasted the 4 #define lines I had >> in my main C file over. However, they don't seem to get an context >> highlighting. And, when I try to build, it exits on an error that >> wouldn't be there if the defines had worked. >> >> This is all with MPLABX by the way. >> >> So here's the thing. The three other #includes in my main file work >> fine. I have put my new header in the same folder and used double >> quotes to include it. I have another file that I included locally >> previously, and it's working fine. My header file appears in the >> project tree under header files. I can't see anything bad in the >> properties. >> >> Still, it seem like the compiler isn't actually processing that file. >> >> Anyone have any thoughts? I'm really not sure what to try next. >> >> Thanks! >> >> Josh >> -- >> A common mistake that people make when trying to design something >> completely foolproof is to underestimate the ingenuity of complete >> fools. >> -Douglas Adams > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist --=20 Jason White --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .