- User Since
- Dec 4 2017, 4:13 AM (81 w, 18 h)
Wed, Jun 19
Mon, Jun 17
Fri, Jun 14
Wed, Jun 12
Wed, Jun 5
@alexei, Applied to a lulzbot-dark theme.
Wed, May 29
May 24 2019
May 22 2019
@alexei Sorry for the delay again, I found a probable solution for icons, testing it now.
Still searching for a good sidebar fix, which not affects any other layouts.
May 10 2019
@karrad Fixed, check it please.
May 3 2019
May 1 2019
@karrad Fixed. Now layer height in quality bar calculates from extruders layer heights.
Apr 22 2019
Sorry for delay with that. Problem caused by unusual dpi settings. Can reproduce this only on ubuntu 16 with non-standard dpi.
Trying to fix it, but don't have any full fix (for icons and for window size) yet.
Apr 10 2019
@karrad, Try to clear cache, please.
Apr 8 2019
@karrad, Probably found a fix, can you check this one please?
Mar 26 2019
@karrad We added a mechanism to load more than one model when first adding the printer.
That can be customized in "cura/resources/meshes/initial_models_for_first_run.json" (we load 2 rocktopuses but of course can be possible to load different models).
Do we need set extruder for each model? It's may be difficult to realization because some application structure features.
Located in T1713 branch.
Mar 22 2019
Mar 14 2019
The original problem was associated with different dpi (especially with a low) and non-adaptive interface. The layout was changed, it seemed to be ok.
I had no problems on Debian Stretch and Ubuntu 16.04 (0.75, 1, 1.25 screen scale), but can anyone test it please?
I push it to separate branch (T3706) to avoid critical bugs in master.
Mar 5 2019
Feb 20 2019
Feb 19 2019
@karrad I think it's happens only with values more than 10, it's caused by restriction in code. Valid values for the field in range from 1 to 10. If value out of range cura use older value. We can change it, if that need.
Feb 12 2019
Feb 11 2019
@karrad We have already conversing this problem earlier and came to the conclusion that we can't do it right. We need to rework placing function and scale to max function for this. Unfortunately, I could not find in which task we were faced with this.
Feb 4 2019
@karrad "nozzle_disallowed_areas" is not intended for that. I added a "extruder_disallowed_areas" feature. It allows to add a disallowed areas per extruder. These zones are activated only when the corresponding extruder is involved.
You can check it in T5549 branch.
Jan 31 2019
@alexei I build it on my local machine and tested it on debian, all works fine. Can anyone test it on other platforms?
Jan 30 2019
@alexei My bad. Which platforms affected? Can you please post link to QT bug tracker? I will test it on my side soon.
Jan 28 2019
Multiple files load works now, you can check it in T3549 branch.
Jan 11 2019
@karrad Fixed. It should not affect other texts and colors.
Jan 10 2019
Jan 8 2019
Dec 13 2018
@karrad Category prioritization added. Branch T4863.
You can add category and set category priority in "Categories_priority.json". If the priorities are same in two or more categories, they will be sorted alphabetically.
Nov 21 2018
@karrad Did we need a separate branch for this?
Nov 16 2018
Nov 13 2018
Sorry, forgot to say: fix located in T4367 branch and affects only filament label and time label anchors.
I can't replicate this on my debian, but i probably have a fix. Check it out, please, and if this does not help, indicate which system and screen resolution you are using.
Nov 8 2018
We tried to work with calculating but have a problem with quaternion to degrees translation (problem with normalization).
We added a fix with rotation fields to every model, check it please (T3214 branch). We think it should work.
Nov 6 2018
@karrad. Rotate tool works good with one object because keep value only for tool but not for each model.
We can add fields for values to object (and tool read this values for each object) or we can work with calculating values from object position.
Oct 24 2018
@karrad We added a toolhead priority mechanism. Now sorting function use field "priority" if it exist and "name" of extruder metadata.
Oct 22 2018
@karrad We found an "App Nap" function which unload application from RAM for more productivity.
Disabling this function for all applications fix that issue.
We also found a way to fix it and disable "App Nap" only for Cura by adding a string into file when application builds.
Can you please rebuild it and test?
Oct 12 2018
Oct 9 2018
@karrad This fix does not affect any other labels and windows, it just resize scale tool window. Can you add configuration of you machine?
Oct 8 2018
@karrad, I think this little fix can help. But the reason of such problems may be a different font DPI.
Sep 27 2018
@karrad Check this one, please.
Sep 21 2018
@karrad, I tried to replicate this, but have not issues with 2 printers on different ports. I tried SD print + USB print and all works correctly. When inspecting code I do not find any problems.
I should test it on 3 machines when we recieve parts with new Archim board. I will also continue to look for the problem in the code.
Sep 7 2018
@karrad Toolhead selection and printer selection now have more space in dialog.
Aug 28 2018
Do we need exclude Lulzbot printers from "Other" section?
Aug 3 2018
@karrad I think it's fixed. Now model rotate works using Shift+LMB and camera move works using Shift+RMB or mousewheel button.
Aug 2 2018
@karrad Fixed. Now values are reset together with model position.
Jul 24 2018
@karrad Fixed. Test it please, on my local build it works correctly.
Jul 10 2018
@karrad, I think this one should help.
Jul 6 2018
Jun 21 2018
@karrad It didn't take much time. I Hope I understand you clearly.
Jun 20 2018
@karrad No, I don't see any way to improve this. Relative positioning by mouse works well and we don't need to add any other ways to use it.
@karrad No, I don't see any way to improve this.
Jun 15 2018
@karrad I found a way to fix it. Now we have absolute positioning like in 2.6 version. Do we need a checkbox for relative positioning?
Jun 14 2018
Jun 12 2018
@karrad Can somebody test it again, please?
Jun 6 2018
@karrad I tried to find optimal algorithm for grouping. Most of it requires too much CPU (really a lot) resources for normal result, other ones grouping models not so accuracy as we need. I think I can add something which can combine both options. It will take about a week.