Peter Uithoven

I put my very quick and dirty mockup on github. https://github.com/peteruithoven/VisiCutOrderMockups

The problem might be that you overrule any other orderings, like in mappings. Which I find slightly unclear.That's why I was suggesting hiding the up and down buttons in the...

@mgmax I agree splitting up the order stuff is confusing. But if you split it up, you can't store order in the saved mappings. But then again I'm not sure...

A new mockup. This allows you a bit more control, with the cost of a bit more complexity.  ![Screen shot 2013-03-24 at...

Hi Rene, I totally get the issue, I've been having issues with the mapping and settings interface for quite a while, we did brainstorm om some designs, but never implemented...

To add to this, for the _Laser Settings_ tab it's important that multiple can be shown. So this same function would be called multiple times and a "," could be...

I would be very interested in the gui designs, maybe we can help? Keeping it simple for first time users for example.

If I understand the structure of Visicut correctly this is the current structure: - lasercutter - material - thickness - profile (cut, engrave, mark etc) - settings (power, speed, etc)...

I've added a issue that explains my idea: #198

Seems it's related to the _Everything else_ mapping. When I make a saved mapping (by color property) like: - Black: cut - Green: engrave - Bitmap: engrave - Blue: mark...