Macro for cleaning and purging nozzle
-
@exerqtor said in Macro for cleaning and purging nozzle:
@fcwilt I shot a short clip yesterday before i fixed the bug in line 169. But it shows what i'm trying to do, the clip was with the hotend off since i wanted to check that it didn't try to purge or flipped out while it was cold.
As for the brush and bucket combo it's derived from this: https://github.com/VoronDesign/VoronUsers/tree/master/abandoned_mods/printer_mods/edwardyeeks/Decontaminator_Purge_Bucket_&_Nozzle_Scrubber
Thanks.
I see the brush, look like brass but I don't see any little buckets.
What did you use for the brush? Any concerns for damaging the nozzle?
Frederick
-
Not a video, but it's at least the buckets!
Not really too woried about nozzle wear to be honest, but if it turns out to be a problem other brush types is a posibility
-
-
@fcwilt
Goodie!As a sidenote, i downloaded the EditPad Pro demo yesterday and it for sure has alot more to offer than what i've been using! BUT, have you made or dug up a syntax highlighting profile for RRF?
-
@exerqtor said in Macro for cleaning and purging nozzle:
@fcwilt
Goodie!As a sidenote, i downloaded the EditPad Pro demo yesterday and it for sure has alot more to offer than what i've been using! BUT, have you made or dug up a syntax highlighting profile for RRF?
Yes - I have created one - it's not perfect - but anything missing is easy to fix.
You ready to take me up on my offer?
Frederick
-
Here is the file. I had to add an extension of .txt to get it to upload - just remove the .txt and put it into:
C:\Users\yourwindowsname\AppData\Roaming\JGsoft\EditPad Pro 8
Frederick
-
@fcwilt said in Macro for cleaning and purging nozzle:
@exerqtor said in Macro for cleaning and purging nozzle:
@fcwilt
Goodie!As a sidenote, i downloaded the EditPad Pro demo yesterday and it for sure has alot more to offer than what i've been using! BUT, have you made or dug up a syntax highlighting profile for RRF?
Yes - I have created one - it's not perfect - but anything missing is easy to fix.
You ready to take me up on my offer?
I'm tempted, have to test it out a little bit before i decide on anything
@fcwilt said in Macro for cleaning and purging nozzle:
Here is the file. I had to add an extension of .txt to get it to upload - just remove the .txt and put it into:
*C:\Users\yourwindowsname\AppData\Roaming\JGsoft\EditPad Pro 8*
Don't look like that worked, i've created the filetype Gcode and added " .g;.gcode " file masks. And if i try going to "Colors and Syntax->Customize->Import" it looks for a .ini ?
EDIT:
I found and followed the guide on their website, but it don't pick it up when i refresh. Might be that it's simply left out of the demo or something.Could you take a screenshot of how the macro we've been working on looks on your end so i can see how it is maybe?
EDIT 2:
Now i got it! Allways fun trying out and learning new stuff ey? #facepalm -
@exerqtor said in Macro for cleaning and purging nozzle:
EDIT 2:
Now i got it! Allways fun trying out and learning new stuff ey? #facepalmSo you got the syntax file to work?
Frederick
-
@fcwilt said in Macro for cleaning and purging nozzle:
So you got the syntax file to work?
Yup! Working on trying to get the color pallete to match the DWC editor atm.
-
@exerqtor said in Macro for cleaning and purging nozzle:
Yup! Working on trying to get the color pallete to match the DWC editor atm.
atm??? Automatic Teller Machine???
The syntax editor has predefined palettes which are crafted with usage in mind, not colors, so much.
If you read about the issue in the help for the Syntax Coloring Scheme Editor they talk about the rational behind their system.
Frederick
-
@fcwilt said in Macro for cleaning and purging nozzle:
atm??? Automatic Teller Machine???
At The Moment
The syntax editor has predefined palettes which are crafted with usage in mind, not colors, so much.
If you read about the issue in the help for the Syntax Coloring Scheme Editor they talk about the rational behind their system.
Can't look at the Syntax Coloring Scheme Editor since it's not included in the demo.
The reason i want it to look like it does in DWC is mainly so that i have one "reference" so to say. Between what i make in my editor and what DWC / RRF does.
-
@exerqtor said in Macro for cleaning and purging nozzle:
Can't look at the Syntax Coloring Scheme Editor since it's not included in the demo.
Yet another great reason to take me up on my offer.
I just discovered a small "bug" in my scheme - but the scheme editor will make short work of it - I think.
The system is based on regular expressions which I have not done a lot with - so I am learning as I go.
Frederick
-
@fcwilt
Yeah it's getting more and more tempting, not gonna lie!I saw your syntax profile has some minor bugs that should be pretty easy to iron out i guess. Don't know how "translateable" the syntax highlighting part is from the DWC sourcecode over to that of EditPad though.
Would be nice to make a "solid" RRF syntax and have it uploaded to the database
-
@exerqtor said in Macro for cleaning and purging nozzle:
@fcwilt
Yeah it's getting more and more tempting, not gonna lie!I saw your syntax profile has some minor bugs that should be pretty easy to iron out i guess. Don't know how "translateable" the syntax highlighting part is from the DWC sourcecode over to that of EditPad though.
Actually I was mistaken. It's the DWC Editor that has it wrong. It threw me off for a bit because mine worked differently. A little more study shows mine is correct - or at least "less wrong".
Consider this from the DWC editor:
The text global.g_tool_exists is the name of a variable and should be all one color - the color assigned to variables.
But the global part seems to be treated the same as if. Both assigned the color for reserved words.
The 0 seems to be treated as a number even though it is part of the variable name
The exists seems to be treated as a function even thought it is part of the variable name.
Now here it is in EditPad Pro
In the second line you can see exists is recognized as a function but works fine as part of the variable name
Frederick
-
@fcwilt said in Macro for cleaning and purging nozzle:
@exerqtor said in Macro for cleaning and purging nozzle:
@fcwilt
Yeah it's getting more and more tempting, not gonna lie!I saw your syntax profile has some minor bugs that should be pretty easy to iron out i guess. Don't know how "translateable" the syntax highlighting part is from the DWC sourcecode over to that of EditPad though.
Actually I was mistaken. It's the DWC Editor that has it wrong. It threw me off for a bit because mine worked differently. A little more study shows mine is correct - or at least "less wrong".
Consider this from the DWC editor:
The text global.g_tool_exists is the name of a variable and should be all one color - the color assigned to variables.
But the global part seems to be treated the same as if. Both assigned the color for reserved words.
The 0 seems to be treated as a number even though it is part of the variable name
The exists seems to be treated as a function even thought it is part of the variable name.
Now here it is in EditPad Pro
In the second line you can see exists is recognized as a function but works fine as part of the variable name
Hm yeah i see what you mean, i must admit i prefer the way it's shown in DWC though.
The operators are different in DWC too:
While in EditPad they are all one color.
Given that you're an actual programmer, have you taken a look at the DWC source code for any "pointers"?
-
@exerqtor said in Macro for cleaning and purging nozzle:
Hm yeah i see what you mean, i must admit i prefer the way it's shown in DWC though.
You don't mind that one thing, a variable name, is incorrectly identified and has colors applied to it for four different things - reserved word, variable name, numeric value and function?
Frederick
-
@fcwilt
Clearly not to the extent it does youFor the record:
@chrishamm said in Making Notepad++ look like DWC g-code editor?:@exerqtor You can have a look at https://github.com/Duet3D/DuetWebControl/tree/master/src/components/dialogs/FileEditDialog for details about the syntax parsing/highlighting in DWC. Because the current CodeMirror component is rather outdated now, I may eventually replace it with something else in v3.5.
So that behaviour might be something that get's reworked in v3.5.
-
@exerqtor said in Macro for cleaning and purging nozzle:
So that behaviour might be something that get's reworked in v3.5.
That is interesting. Thanks for the info.
It does need to be worked on, as it failing to correctly analyze the code and to properly highlight the syntactical elements.
I could create a scheme which duplicated the way the DWC editor works - but then they would both be wrong.
And then that would be two things that needed fixing instead of just one! >>
Frederick
-
@fcwilt
Yeah i totally agree with what your saying.And just to clarify i prefer how it LOOKS in DWC, as it makes it easier for my peasant brain to break up/visualise the different parts of the code.
I think we have a somewhat different view of this since you actually know what you're looking at, while i'm trying to make best of what i'm seeing based on self thought knowledge learned by trial and error.
-
@exerqtor said in Macro for cleaning and purging nozzle:
And just to clarify i prefer how it LOOKS in DWC, as it makes it easier for my peasant brain to break up/visualise the different parts of the code.
You don't have a "peasant" brain - that much is obvious.
But can you explain how applying four different colors, three of them wrong, to that one variable name helps you?
The goal is to identify syntactical elements as clearly as possible without overly cluttering the display with too many colors.
For example, RRF has a handful each of reserved words and functions. You wouldn't want to color each reserved word or function differently. All reserved words should be of one color, all functions of perhaps another color.
These are the elements I am currently identifying (sorry it's so small - it's a screen shot):
Notice that I am picking out three types of numbers: hexadecimal, float and integer. Now the syntax editor allows assigning a different color to every identified kind of element but the default palette colors them all the same - to reduce clutter.
You have a large selection of palettes to chose from - and you can create your own:
So between being able to design you own syntax identification scheme and your own palette you should be happy as a clam at high tide!
Frederick