Page 1 of 1

Notepad++ UCCNC Macro Style + Autocomplete Addin

PostPosted: Mon Sep 26, 2016 6:35 pm
by Robertspark
As per the title.....

Within the zip file is a PDF explaining what to do (+ with pictures ... :roll: )

There is the UCCNC.XML file which you need to copy and paste into the: C:\Program Files (x86)\Notepad++\plugins\APIs folder.

Then there is the UCCNC Style.XML file which you will need import via the Languages + User Defined Languages.

Also I'd recommend that you change the Settings >> Style Configurator to Deep Black Theme or change the Styles

256kB file limit! ... googledrive link below:

https://drive.google.com/open?id=0B9eqGqWQVBbWZHJKbFZZNDl6OEE

Re: Notepad++ UCCNC Macro Style + Autocomplete Addin

PostPosted: Mon Sep 26, 2016 10:49 pm
by Vmax549
Hey ROB can that thing make a decent cup of coffee???

(;-) TP

Re: Notepad++ UCCNC Macro Style + Autocomplete Addin

PostPosted: Mon Sep 26, 2016 11:16 pm
by Robertspark
... well I did burn the midnight oil on it, but once I got going at understanding notepad++ I kind of thought I better finish .... another string to the bow and something learnt....

(must admit I have updated the style.XML this evening.... if you have downloaded it before about 9pm (~3 hrs ago... I'd download it again, delete the user defined language and add in the new Language style as there were a few things that were not working right......)

TP, thanks very much for the tip on using the error log file...... the question is the line numbers don't correspond to the macro, is that because it ignores whitespace?

Re: Notepad++ UCCNC Macro Style + Autocomplete Addin

PostPosted: Tue Sep 27, 2016 12:07 am
by Vmax549
HI Robert, actually I have no real idea BUT it seems to be a constant 10 line offset . Being teh first line of script is teh 10th line in the errolog line definition.
My GUESS is that it is accounting for teh function() that teh Macro enviroment is wrapped in when running in UCCNC and that appears to be 10 lines of code BEFORE it calls teh macro script into play. Being that the debugger is not strictly macro based it accounts for everything involved.


(;-) TP