A few bugs/nits

As always, let me preface this by thanking you for Kiri-Moto. It’s fantastic! I’ll be backing that up with my wallet, somehow, soon.

That being said… a couple of issues. :wink:

a) I believe the units for the leveling operation’s stepdown are stuck in mm. The leveling passes appear as stripes in my previews because there are 25 times as many layers as there should be.

b) The leveling and roughing operations don’t seem to know about one another. Depending on how they’re ordered, each cuts air in spaces that the other has already removed. I was hoping to use leveling to clear the entire top of the stock down close to the part before roughing. (Otherwise the shoulder of my collet would hit the top of stock when the roughing gets deep.) And actually, I just noticed that the outlining operation also cuts air where the leveling operation has been. Of, am I simply working under a misunderstanding: I thought that the operation passes all knew what material had already been removed, and could optimize based on that.

c) If two outline operations are configured, there’s only one hide-me checkbox at the bottom of the screen. Seems like they could each have their own.

Finally – since you chastised me yesterday :slight_smile: for not using the docs, I went looking for them from within the UI today. It took me about 5 minutes of checking every likely menu before my mouse happened to hover on the logo. Sigh. It was very frustrating. It’s an elegant touch making the logo a menu icon, but it’s an example, IMHO, of “clean design” gone too far. If the logo were up in the left or right corner, I might have tried it, because that’s a common place for apps to put major menus. But it’s just text, so it looks like a page title. It wouldn’t hurt to put a little “?” icon somewhere on the screen (maybe in addition to keeping the logo active). ( TL;DR – Don’t hide the help! :slight_smile: )

Again, many thanks for all of your work!

a) this might be a more prevalent issue. do you mind filing github issues? I will be making a push to close a bunch of tickets ahead of 4.4 and these should be easy fixes. I just don’t want to forget.

b) Kiri has never had “rest” machining. in the operation chain, all ops run with zero knowledge other than the stock and selected workarea (pocket, trace) or global for og ops like roughing and outline. I plan a major refactor post 4.4 to tackle this. it’s a complex issue.

c) noted. fixable. see a)

d) was that chastising? not the intent. how’s this …

Screenshot 2025-11-13 at 3.58.38 PM

Sure, I’m happy to file a couple of issues for ‘a’ and ‘c’. As for ‘b’, I was sure it used to work like that, but it’s been a while since I’ve worked with it, and clearly I was wrong. And ‘d’? No worries, I didn’t take it that way.

I think your suggestion above looks a little too much like it’s asking a question: “Kiri:Moto?”.

I guess I’d ask, is title bar space really that scarce? If not, why not have a “? About” label at the far right end, on the far right of Setup? You could drop it, and let the current behavior suffice, on very narrow screens, if that’s an issue.

the customer is always right

Screenshot 2025-11-13 at 6.04.16 PM

new menus live on dev.grid.space and app.grid.space (installable pwa)

1 Like

That’s perfect. I would have found that immediately.

1 Like