ultimaker / uranium Goto Github PK

For the release, I would like to have deb and rpm packages that people can use. These can be built with CPack and do not need to be perfect but would at least provide a starting point.

Platform: Arch Linux 64-bit
Qt: 5.4.1
PyQt: 5.4.1
Diplay Driver: xf86-video-intel 2.99.917

Steps to Reproduce:

• Open the Preferences dialog.
• Switch to the Machine page.

Actual Results:

• The first available machine is selected.

Expected results:

• The current active machine is kept active.

from Cura issue https://github.com/daid/Cura/issues/1003:
MoonCactus commented on 6 Nov 2014

OK I know you like absolute values ;)

PROBLEM: I often fail to remember to go and check the infill and shell speeds after I change the main speed (esp. when I reopen Cura days later). This produces a broken set of values (e.g. lowering the main speed from 60 to 30mm/s, but failing to go and fix former inside speeds that are left at 100mm/s!)

SUGGESTIONS:

1. it would be more efficient imho to specify a proportion of the main speed (mostly b/c this is how we usually think about it: e.g. 150% speed for the insides is a safe guess -- "absolute" values are counterproductive here as we need to compute them ourselves anyway!).
2. Post-fixing the number with a percent sign in the field could trigger such a "proportional" behavior, and without changing the UI. Would be the cleanest way. Note that this could be generalized to other settings as well (e.g. wall thickness as a proportion of the nozzle diameter: 200% for 0.8 when the nozzle is 0.4).
3. Finally, as a "hidden feature": a negative value could be regarded as a proportion of the main speed (e.g. -180 would mean 180% of the main speed value -- or use directly -1.8 as a multiplier). It would be computed as an absolute value just before it is given to the engine. Very easy and convenient, but a bit dirty indeed.
4. at least, color-code a warning in the "main" speed when it gets "out of proportion" of the current infill or shell values (like, e.g. when I specify an initial layer thickness which is too thick with respect to the nozzle size). Hard to guess the acceptable proportion though (50-100%?)

We need to improve the plugin developer guide / documentation and ensure this is proof read by (external?) developers.

Cura window, and Cura installer need an proper icon instead of the default icon.

• Artwork = Menno?

Application Version: 15.05.92
Platform: Arch Linux 64-bit
Qt: 5.4.1
PyQt: 5.4.1
Display Driver: xf86-video-intel 2.99.917

Steps to Reproduce:

• Start the application
• Click-and-drag with the middle mouse button on the central view

Actual Results:

• Nothing happens

Expected results:

• Camera center is moved so the camera is looking at a different center point.

Platform: Arch Linux 64-bit
Qt: 5.4.1
PyQt: 5.4.1
Diplay Driver: xf86-video-intel 2.99.917

Steps to Reproduce:

• Load an OBJ file

Actual Results:

• Mesh is rendered in black due to missing normals.

Expected results:

• Correct rendering of the mesh with proper normals.

Additional Information:

• Screenshot: http://wstaw.org/w/3mk5/

The menu that should pop up when trying to save g-code if there are multiple devices (usb printers / local/ whatever) doesn't show on Ubuntu.

Platform: Arch Linux 64-bit
Qt: 5.4.1
PyQt: 5.4.1
Diplay Driver: xf86-video-intel 2.99.917

Steps to Reproduce:

• Load a model.
• Switch to "Advanced" mode.
• Open the "Quality" tab
• Set "Layer Height" to 0

Actual Results:

• The text box turns red to indicate an error but then slicing starts and the engine will crash every time until the Layer Height is set back to something > 0.

Expected results:

• The text box turns red and slicing does not start.

Additional Information:

• After some discussion with BagelOrb we decided that we should assume error values are incorrect values and not slice if there are any, whereas warning values are things we think are invalid values but which may work. We should make sure we have correct error and warning values on settings.

Shift + right click + drag = translate camera, just like the old cura.

Splashscreen still needs to be updated

• New artwork/logo = menno.

Object is sitting on bottom untill dragged:

Design is now fairly ugly, might want to have a look at that.

I've noticed that under some viewing angles, I cannot rotate or translate along some axis, while others do seem to work. I'd have to rotate the cam, then transform the object, then rotate cam back.

We lack a MacOSX installer. We should make sure we have one for the final release.

Half of the time when I rotate an object, the first angle it snaps to is something like 1 degree instead of 0 degrees.

When you try to view an object exactly from above, by right clicking and dragging down or up and the camera is aligned with the Z axis the view starts flipping upside down every frame you move the mouse, until you drag the view to a normal position again.

I suggest a quick hack which limits the camera angle to 89 degrees instead of 90.

under Resolution, below or above Top/Bottom pattern

(positive is outward, negative inward)

CuraEngine setting name: "XYcompensation"

The scale tools get highlighted when cursor is in the wrong place. When cursor is a bit below the actual tool (in pixels, not in real space).

Some models show wrong overhangs.

Perhaps the normals as described in the STL file are incorrect.

It would then be nice to recalculate the normals so that the right pieces are colored red.

I use a dark theme in Qt, and it sets a light font color. The backgrounds of tool-tips seem to be a static color, so text is completely unreadable. Text in setting boxes also become almost unreadable. It would be good to have those depend upon the theme. Though ideally, the whole UI should be somehow themeable.

Application Version: 15.05.92
Platform: Arch Linux 64-bit
Qt: 5.4.1
PyQt: 5.4.1
Display Driver: xf86-video-intel 2.99.917

Steps to Reproduce:

• Load a model
• Select it
• Move it
• Double click it

Actual Results:

• Nothing happens

Expected results:

• Camera animates to centre on the new location of the model.

Make the back of each face red for example.

This could be implemented for the normal view or for a new view.

Not all views are views that can be activated by users. We need to add an option to the views that enable 'hidden' views, so they cant be selected from view selection.

An example of this is the PointCloudAlignment, which is a tool with an 'attached' view. Only when the tool is activated, it needs to set the view. It doesnt make any sense to have the view active when the tool isnt active.

Platform: Arch Linux 64-bit
Qt: 5.4.1
PyQt: 5.4.1
Diplay Driver: xf86-video-intel 2.99.917

Steps to Reproduce:

• Open the preferences dialog
• Go to the plugins page
• Click on the information button for a plugin with a long description like the "USB Printing" plugin.

Actual Results:

• A dialog is shown with text cut off at the right side.

Expected results:

• A dialog is shown with the description properly wrapped onto a new line.

Additional Information:

• Screenshot: http://wstaw.org/m/2015/05/12/cura_about_plugin.png

We need to split up the repository into the Uranium framework, Cura 3d printing application and other parts.

Traceback (most recent call last):
  File "printer/printer.py", line 3, in <module>
    from PrinterApplication import PrinterApplication
  File "/home/tim/Development/PluggableCura/printer/PrinterApplication.py", line 1, in <module>
    from UM.Qt.QtApplication import QtApplication
  File "/home/tim/Development/PluggableCura/UM/Qt/QtApplication.py", line 14, in <module>
    from UM.Qt.Bindings.Bindings import Bindings
  File "/home/tim/Development/PluggableCura/UM/Qt/Bindings/Bindings.py", line 15, in <module>
    from UM.Qt.Bindings.ResourcesProxy import ResourcesProxy
  File "/home/tim/Development/PluggableCura/UM/Qt/Bindings/ResourcesProxy.py", line 5, in <module>
    class ResourcesProxy(QObject):
  File "/home/tim/Development/PluggableCura/UM/Qt/Bindings/ResourcesProxy.py", line 16, in ResourcesProxy
    @pyqtSlot(int, str, result=QUrl)
TypeError: an integer is required (got type [RANDOM TYPE!!!!])

I get this like 10 times before Cura will start. This is the whole log of such a run.

note that [RANDOM TYPE!!!!] is different on each run.

When scaling an object up or down, the z should change immediately automatically, instead of being recomputed by the module which automatically puts the object on the platform.

Thinking about it, it would be logical to have the origin of an object at the bottom, instead of in the middle. That way you bypass the whole problem.

Platform: Arch Linux 64-bit
Qt: 5.4.1
PyQt: 5.4.1
Diplay Driver: xf86-video-intel 2.99.917

Steps to Reproduce:

• Load two models
• Select one of the two

Actual Results:

• It is not possible to select the other model except when deselecting the current model first.

Expected results:

• The selection switches to the other model when you try to select it.

When an object is way too large, auto-resize it when loaded.

Not when object is just 1.5x larger than the buildvolume in one dimension, for it might still fit by rotating.

White icons can merely be seen on the light shade of grey.

Traceback (most recent call last):
File "/home/jaime/Development/PluggableCura/UM/Qt/QtApplication.py", line 109, in event
event.functionEvent.call()
File "/home/jaime/Development/PluggableCura/UM/Event.py", line 130, in call
self._function(_self._args, *_self._kwargs)
File "/home/jaime/Development/PluggableCura/UM/Signal.py", line 87, in emit
func(dest, _args, *_kargs)
File "plugins/LocalFileStorage/LocalFileStorageDevice.py", line 55, in _onDrivesChanged
self.removableDrivesChanged.emit()
File "/home/jaime/Development/PluggableCura/UM/Signal.py", line 87, in emit
func(dest, _args, *_kargs)
File "/home/jaime/Development/PluggableCura/printer/PrinterApplication.py", line 331, in _removableDrivesChanged
for device in self._output_devices:
RuntimeError: dictionary changed size during iteration

Platform: Arch Linux 64-bit
Qt: 5.4.1
PyQt: 5.4.1
Diplay Driver: xf86-video-intel 2.99.917

Steps to Reproduce:

• Load a mesh.
• Select it to make the translation tool active.
• Drag the Y axis (Blue) handle.

Actual Results:

• The object is moved along the Y axis.

Expected results:

• Nothing happens. In fact, the Y handle should not even be visible.

Camera centers on object in middle of the window instead of middle of the view.
It doesn't take the settings bar into account.

Especially annoying when working on smaller screens (laptop screen).

JWeaver asked for a measure tool in the following post:
http://umforum.ultimaker.com/index.php?/topic/10274-is-there-a-way-to-measure-in-cura/#entry99611

I suggest selecting the first point and displaying the distance as soon as the mouse is over another point. Perhaps display a (dashed) line between the point clicked and the mouse/point hovered over.

Due to the fact that I can't see the command line arguments to the curaEngine, I can't debug why Neith is is not working from the interface.

please add [Show slice engine log...] options as in Cura 15.02.1

When selecting a new object, the camera slowly pans toward the object.
However, now it moves more like
_
...|_
......|_

instead of

..
....\

(dots used for spacing cause whitespace is automatically removed)

The selection of tool handle doesnt work from one side, but does from the other. This is most likely caused by ray intersection with plane, where the direction of the plane normal is used.

Selecting an object is hard. Most of the time it doesn't work.

At least the UMO platform currently shows severe z-fighting. We should check all the platforms we ship and fix any that have z-fighting by moving them down.

Objects on the platform (atleast on umo) have zfighting with platform. Can be seen when viewing the object from below (looking through the platform)

(And also causes minor vizualization bug which helps me in showing that the wrong object has been moved)

I selected the robot, dragged it over the wolf and then the selected robot got relocated instead of the wolf.

Plugins can now only have a single type. We already have cases where this is not quite true; Some plugins might be tools & views at the same time.

Platform: Arch Linux 64-bit
Qt: 5.4.1
PyQt: 5.4.1
Diplay Driver: xf86-video-intel 2.99.917

Steps to Reproduce:

• Load a relatively large (>10MB) file.

Actual Results:

• A message pops up displaying "Loading file" then disappears while the file is still being loaded.

Expected results:

• The message is always shown while the loading process is going on and only disappears when it is replaced by the "Loaded file" message once loading is complete.

We now use the 'correct' ctrl+o for opening files, but the old cura uses ctr+l , so we might want to consider supporting ctrl + l aswell.

just as in the old cura.

Platform: Windows 7
Qt: 5.4.1
PyQt: 5.4.1

Steps to Reproduce:

• Have a machine with certain configurations of Card readers
• Start the application

Actual Results:

• Every time a scan is done for removable drives it will try to access a drive with no actual media inserted. This will cause Windows to popup an error dialog.

Expected results:

• Removable device scanning is silent with no errors.

Additional Information:
Screenshot:

Dragging a (supported) file from folder onto cura needs to be handled.