# First 2 cuts on the maslow **URL:** \ **Category:** No Judgement\ **Created:** [November 25, 2017, 6:11am UTC](https://forums.maslowcnc.com/t/first-2-cuts-on-the-maslow/1215 "2017-11-25T06:11:58Z")\ **Posts on this page:** 6\ **Page:** 2
**Author:** ![Gero](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/gero/32/17487_2.png) [@Gero](https://forums.maslowcnc.com/u/Gero)\ **Post date:** [November 27, 2017, 8:46pm UTC](https://forums.maslowcnc.com/t/first-2-cuts-on-the-maslow/1215/21 "2017-11-27T20:46:41Z")
Quick fix in Editor! (\_ = ‘blank’) Find X, replace with \_X, find Y replace with \_Y, same for J,I,Z and in less than a minute you are done. Is this the right rendering of your part? ![isItIt](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/2X/c/ce9c599166d63a04b236963e0e301386376c1b43.jpg) [Test box.nc](https://forums.maslowcnc.com/uploads/maslowcnc/original/2X/8/8a7b64a81999fbc26071e70db3d1747064a3133b.nc) (31.0 KB) ---
**Author:** ![blurfl](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/blurfl/32/9_2.png) [@blurfl](https://forums.maslowcnc.com/u/blurfl)\ **Post date:** [November 27, 2017, 10:02pm UTC](https://forums.maslowcnc.com/t/first-2-cuts-on-the-maslow/1215/22 "2017-11-27T22:02:49Z")
> [@bar](#): > > hat’s a bug and we need to fix it Take a look within gcodeCanvas.py reloadGcode() in the area of lines 128-133. This looks like an opportunity for some regex wizardry 😄. ---
**Author:** ![Onelonedork](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/onelonedork/32/1358_2.png) [@Onelonedork](https://forums.maslowcnc.com/u/Onelonedork)\ **Post date:** [November 27, 2017, 11:25pm UTC](https://forums.maslowcnc.com/t/first-2-cuts-on-the-maslow/1215/23 "2017-11-27T23:25:33Z")
That’s exactly what I was trying to create. ---
**Author:** ![vertex](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/vertex/32/972_2.png) [@vertex](https://forums.maslowcnc.com/u/vertex)\ **Post date:** [November 27, 2017, 11:46pm UTC](https://forums.maslowcnc.com/t/first-2-cuts-on-the-maslow/1215/24 "2017-11-27T23:46:01Z")
would it make sense to collect these kinds of py scripts in a github Maslow toolbox? also [v-plotter.py](http://v-plotter.py) Something that can be installed in one go? Or maybe piggyback with the GC install? Maybe with a bit of a gui style launcher to make them more accessable to people who don’t have commandline skills. I would not mind having a few launch buttons in a folder that save me some time from figuring out what command to write. or with a little [read.me](http://read.me) file with pre-chewed commands to cut and paste. This may eventually help people to get familiar with the commandline, after ten times pasting a command then it starts to stick in the neurons and fire on it’s own one day. ---
**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\ **Post date:** [November 28, 2017, 12:06am UTC](https://forums.maslowcnc.com/t/first-2-cuts-on-the-maslow/1215/25 "2017-11-28T00:06:45Z")
Well that [gcodeCanvas.py](http://gcodeCanvas.py) is a part of Ground Control. Ideally I think we should just make Ground Control completely bullet proof so that any file anyone tries to open would work. The trick is to get the regex wizardry just right so that we can clean up and parse any file automatically like @blurfl says ---
**Author:** ![blurfl](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/blurfl/32/9_2.png) [@blurfl](https://forums.maslowcnc.com/u/blurfl)\ **Post date:** [November 28, 2017, 1:07am UTC](https://forums.maslowcnc.com/t/first-2-cuts-on-the-maslow/1215/26 "2017-11-28T01:07:59Z")
@Bar just merged a PR to address the missing spaces issue. If you like, you could try it on the file that didn’t have spaces to see if it renders correctly now. Let us know how it comes out 😄. [Previous page](https://forums.maslowcnc.com/t/first-2-cuts-on-the-maslow/1215.md?page=1)