Suggestion: Layers view in mm

[Thisismydigitalself]

Please add to layer number marker the total height in mm as well.

[konvoj]

+1

[maukcc]

not total height, but height at that layer or best: "current height"/"total height"

[Thisismydigitalself]

not total height, but height at that layer or best: "current height"/"total height"

Yes, that was my intention, sorry. "current/marker height" thank you.

[Ghostkeeper]

Our project manager removed this from our planning because it was not seen as important enough.

[maukcc]

The difference between excellent and just good enough is in the details :)

[ianpaschal]

The difference between excellent and feature creep is also in the details :)

[darkdvd]

Not important but make a huge difference !

Actual view :

View in mm :

View in Layer & mm :

So please add the possibility to show the height in mm.

[samuelcarreira]

I want this feature too

[Guyohms]

I'm using adaptive layers feature and for tuning the adaptive layers parameters, this feature would help so much.

I guess it's simple to implement, because since Cura knows the thickness of each layers under the current one, it should be just a summation.

A parameter in Cura's setting to choose between the 3 modes as shown by darkdvd would be excellent !

[Rodamyot]

++++++++1

[steblerjun]

++++++++1 please add the possibility to show the height in mm in preview mode!

[logiclrd]

I don't even think this needs to be a configurable option. Just always show both the layer number and the Z value it's printed at.

Some people (like myself) feel comfortable poking through the G code file to check things out, even insert commands here and there. Cura writes comments like ;Layer:0 to the G code, but these numbers correspond to the raw layer of the model, and the Preview pane has its own numbering scheme. It starts at 1, and if you use a raft, the raft's layers get counted first, etc. Currently, it's really difficult to figure out which layer in the G code corresponds to what is being shown in the preview. Please, please just make it say what the Z value is, so I can go to the G code and search for Z1.23 or what have you.

[logiclrd]

@Ghostkeeper Can you take this back to the project manager and ask them to reconsider? As far as I can see it's a tiny feature with no logic required, and it would make many people's lives so much easier.

[konskarm]

Hi @logiclrd. This is already in our backlog, but there are other priorities at the moment. Devs, see CURA-6535.

[logiclrd]

Cool beans, thanks for the update :-)

[Thisismydigitalself]

3 years since i started this thread. I guess it's better late than never. Looking forward.

[coskier]

Although who knows how long the backlog will take to clear...

[kpishere]

I'm also looking for this feature. You see, the printer shows its current working height in mm. You want to reference the cura preview in the same units. Esp. for adaptive layer heights, the math isn't just an annoyance.

[Ghostkeeper]

Our project manager has deferred this issue again, since they don't expect to be working on this any time soon. We'll leave this ticket open on Github since it is a real issue (and one that we hear more often), but mark it as deferred to make it clear that it's not expected to be implemented any time soon.

[logiclrd]

Does deferred mean that it's not in the backlog any more? This continues to be a regular issue. I need this feature on many projects. I'm not the only one, looking at the comments on this issue.

[logiclrd]

Maybe I can figure out how to do it myself...

[logiclrd]

So, I've been poking at it for an hour or two, and I'm not 100% confident I'm understanding where exactly the label is defined and how it gets its value. Is it the SimulationSliderLabel inside the upper/lower handle Rectangle? I see it getting its value through what looks like data binding -- the LayerSlider.qml file says simply value: sliderRoot.upperValue.

So, to implement this feature, sliderRoot would need to be given a new bindable property that provided the desired text including the actual physical height, and the implementation of that property would need to include a look-up into a list of Z values by layer number, and then that data would need to be piped in from a place that knows it.

[Ghostkeeper]

Does deferred mean that it's not in the backlog any more? This continues to be a regular issue. I need this feature on many projects. I'm not the only one, looking at the comments on this issue.

Practically, yes. It means we acknowledge it to be an issue but doesn't get enough priority for it to be planned in the priority list. We give it that label in order to communicate that you really shouldn't be expecting this to be implemented soon. In practice, most deferred bugs eventually get fixed in a refactor left or right. Most deferred feature requests are still open probably, but some get implemented later if priorities change. It wouldn't surprise me if this eventually makes it in through a redesign of the layer view slider.

So, I've been poking at it for an hour or two, and I'm not 100% confident I'm understanding where exactly the label is defined and how it gets its value. Is it the SimulationSliderLabel inside the upper/lower handle Rectangle? I see it getting its value through what looks like data binding -- the LayerSlider.qml file says simply value: sliderRoot.upperValue.

Exactly. sliderRoot.upperValue is defined at the top of the file, where it's set to the maximum value (the total number of layers) by default. The state of the layer view is here tracked in QML which is bad practice according to our guidelines but not the end of the world either.

So, to implement this feature, sliderRoot would need to be given a new bindable property that provided the desired text including the actual physical height, and the implementation of that property would need to include a look-up into a list of Z values by layer number, and then that data would need to be piped in from a place that knows it.

I would rather implement a new pyqtSlot function in UM.SimulationView that takes a layer number and returns the Z coordinate of that layer, or perhaps a Z range for spiralize and wireframe modes. The label can then just display the result of UM.Simulation.getLayerZ(sliderRoot.maximumValue) and it'll update automatically when the maximumValue changes.

[aandea]

I use a Creality printer. When I switch the layer from 0.2 mm to 0.12 mm, the calculations become a burden to track progress. I would love to see this feature implemented as well !

[maruhe]

+++1 with adaptive layers i becomes more important also users decide what is important for them! not a project manager..

[lmcjerl]

++1 This should be a very easy display update!