GitHub-Proxy/Cura
1
0
Fork 0
mirror of https://git.mirrors.martin98.com/https://github.com/Ultimaker/Cura synced 2025-05-16 17:36:41 +08:00
Code Issues Packages Projects Releases Wiki Activity
2,072 Commits 290 Branches 260 Tags
Commit Graph

455 Commits

Author SHA1 Message Date
Jaime van Kessel
819c9568b1 Backend now correctly handles machine instance change 
CURA-1323
 2016-04-04 10:29:42 +02:00
Jaime van Kessel
ca70b275d8 Revert "Changed wait for subprocess to poll" 
This reverts commit e463c93f77a8015b00ab49aa7b8f9f6433cba26b.
 2016-04-01 13:58:11 +02:00
Jaime van Kessel
e463c93f77 Changed wait for subprocess to poll 
The wait is a suspect in a MAC issue. CURA-1300
 2016-03-31 17:35:57 +02:00
Jaime van Kessel
d3a6f63d1f 3MF no longer fails when there is no transformation matrix 2016-03-24 16:41:25 +01:00
Jaime van Kessel
c1af2c4ae0 3mf reader now uses correct coordinate frame 2016-03-24 09:46:28 +01:00
Jaime van Kessel
3663f8ca20 Backend now logs return codes of processes 
CURA-1133
 2016-03-23 15:11:56 +01:00
Ghostkeeper
a89e128f72
Add period after description 
This is in line with most other descriptions.

Contributes to issue CURA-1190.
 2016-03-22 17:02:42 +01:00
Ghostkeeper
a60f63c71b Add internationalisation for ChangeLog plug-in 
Some of these strings were not translated.

Contributes to issue CURA-1190.
 2016-03-22 15:38:01 +01:00
Ghostkeeper
a056ddc885
Add period at end of plug-in description 
For consistency. All other plug-ins have this (no really, now).

Contributes to issue CURA-1190.
 2016-03-22 15:10:57 +01:00
Ghostkeeper
b457af1081
Add period at end of plug-in description 
All other plug-in descriptions have that too. So for consistency.

Contributes to issue CURA-1190.
 2016-03-22 15:07:05 +01:00
Ghostkeeper
b67ba04222
Fix key in metadata 
The description key was broken (typo).

Contributes to issue CURA-1190.
 2016-03-22 15:05:22 +01:00
Ghostkeeper
47e856c927
Add period at end for consistency 
Other plugin descriptions also have a period at the end.

Contributes to issue CURA-1190.
 2016-03-22 13:35:28 +01:00
Jaime van Kessel
8f9210af6b Socket is now re-created regardless of process state 
The previous fix for this could cause an infinate slice loop on windows. CURA-1133
 2016-03-22 11:29:16 +01:00
Jaime van Kessel
dce4fa9479 Added forced re-creation of socket 
CURA-1133
 2016-03-21 16:32:10 +01:00
Jaime van Kessel
174f150ead Error now also causes terminate to be called 
CURA-1133
 2016-03-21 15:44:27 +01:00
Jaime van Kessel
3ecd746f21 Added even more logging 
CURA-1133
 2016-03-21 15:36:07 +01:00
Jaime van Kessel
46bf7e440e Added more logging & removed duplicate slicing canceled signals 
CURA-1133
 2016-03-18 12:00:10 +01:00
Jaime van Kessel
2df91d8e0b Merge branch '2.1' of https://github.com/Ultimaker/Cura into 2.1 2016-03-17 14:44:37 +01:00
Jaime van Kessel
89256b5423 Added explicit home bed before rest of bed leveling 
CURA-1102
 2016-03-17 14:44:09 +01:00
Ghostkeeper
4507560e30
Codestyle: Whitespace around operators 
A space on both sides around binary operators. A space after the comma.

Contributes to issue CURA-1102.
 2016-03-17 11:53:11 +01:00
Jaime van Kessel
9a6615213c Bed should no longer be damaged when leveling 
CURA-1102
 2016-03-16 15:18:11 +01:00
Jaime van Kessel
7c22fe1eb5 Removable drive plugin is now forced to use machine preference for output type 
Fixes CURA-1165
 2016-03-15 16:43:14 +01:00
Jaime van Kessel
4fb9a6a699 Per object settings now also uses visible depth 
CURA-1160
 2016-03-15 16:15:13 +01:00
Jaime van Kessel
b863d239b0 Added more logging to engine connection 
Should make it easier to debug future issues. CURA-1133
 2016-03-15 12:53:22 +01:00
Ghostkeeper
54ceafbcd0
Handle the flux capacitive fizbit ambigruously 
Makes the unambigruous fizbit warp correctly when subjugated to the flux capacitor. The limit of the reciprocative function seems to be computed correctly now.

Contributes to no issue.
 2016-03-11 17:39:53 +01:00
daid
8980600292 CURA-1104: Fix the incorrect "failed to eject drive" message for windows. 
The C windows API call was wrong. The lpBytesReturned parameter was set to
NULL. While the docmentation at:
https://msdn.microsoft.com/en-us/library/windows/desktop/aa363406(v=vs.85).aspx
states that it CANNOT be NULL if lpOverlapped is NULL. Overlapped is for
async operations. So the easiest way to fix this is to supply a proper
pointer.

I've also removed unused includes. And supplied the DeviceIoControl with
proper ctypes calling information to prevent other python->c problems.
 2016-03-11 15:13:09 +01:00
Jaime van Kessel
3b66e887b0 Added logging 2016-03-11 14:49:21 +01:00
Ghostkeeper
3690eafb72 Add filter_by_machine parameter to USBPrinting 
This was an oversight. When the filter_by_machine feature was added, we didn't think of the USB printing output device. The feature has no meaning here, since USB printing only supports g-code. Just ignore it.
 2016-03-10 10:46:54 +01:00
Jaime van Kessel
3df0b4de66 Fixed removable drive for OSX 2016-03-08 16:59:16 +01:00
Ghostkeeper
9bf12cf7b2
Remove double profile entry from D̩̙̹͈̜ͭ̌̃ͫ͊I̤̝̻͎̖̗͖͌̐̔C̪̐ͣ̅͛̆̇̅Ț̻̄͌̐ͪ̋ͨͫȈ̭̬̪͕̖̙̪̻̿ͥO̱͖̟͓̞͗ͧ͋ͮṆ̱̥͍̦͎̋ͭ̒͛A̻̯̳̩͈̱̤͎̽ͥͨ̋͐̀R̦̯̠ͩͮͮ̓̃ͭÝ̫̜̺̻̼̉̄̏͌ͭ̏͗̊ ̣̪̠̙̜͐ͥŐ͎̞̺̦̬̜͋̓F̩̣͖̤͇͍̍ͬ̽̉̏̿̾̓͒ͅ ̩̬̥̯ͮ̀ͮͮ͑̃̎ͅD͈̪ͧͣO̘̪̟̗̹͓̅̊ͅǑ͈M̟̦̭͙͈͕̖̊̅ͤ̓ͅ 2016-03-04 16:22:31 +01:00
Arjen Hiemstra
66a9c63048 Add not using numpy.insert explanation to ProcessSlicedObjectJob 
Contributes to CURA-708
 2016-03-03 11:52:56 +01:00
Jaime van Kessel
ef206f5ab7 Merge branch '2.1' of https://github.com/Ultimaker/Cura into 2.1 2016-03-03 11:36:54 +01:00
Jaime van Kessel
c4c5ba6c22 Top layers are now correctly updated when object is selected 
CURA-992
 2016-03-03 11:36:28 +01:00
Ghostkeeper
f6fc5fea06 Fix slicing not interrupting first layer processing job 
The layer processing job that was triggered by switching to layer view was not stored in the field. The field is where the start of slicing looks for jobs to abort.

Contributes to issue CURA-864.
 2016-03-03 11:31:59 +01:00
fieldOfView
5cb1e9e2a6 Tweak layer slider appearance 2016-03-03 09:00:52 +01:00
fieldOfView
90fda4cb3d Remove defaults section from current settings before adding it to a gcode file. 
Contributes to CURA-936
 2016-03-02 21:18:16 +01:00
Ghostkeeper
7a913bf99a Fix comment 
It had some variable name pasted into it by accident.

Contributes to issue CURA-936.
 2016-03-02 17:31:58 +01:00
Jaime van Kessel
9c5e169f2b Loaded profiles are now marked as dirty so they are saved correctly 
CURA-936
 2016-03-01 16:24:43 +01:00
Jaime van Kessel
e90fd95495 Profile importing now checks if it's the right file type 
Contributes to CURA-936
 2016-03-01 15:16:50 +01:00
Jaime van Kessel
41d00af345 Moved timer back again, as arjen fixed the real issue 2016-03-01 10:57:29 +01:00
fieldOfView
51ad894711 Properly disable Per Object Settings toolbutton on first start 
On an empty profile, the cura/active_mode preference is not set so the code disabling the button was not called.

Fixes CURA-901
 2016-03-01 10:34:00 +01:00
Jaime van Kessel
7985a961c4 Merge branch '2.1' of https://github.com/Ultimaker/Cura into 2.1 2016-03-01 09:31:05 +01:00
Jaime van Kessel
fa59416dc4 Added warning to logging if no one at a time print is possible 
CURA-972
 2016-03-01 09:30:33 +01:00
Arjen Hiemstra
3afd3f2209 Use the right style for the layer view slider and add a busy indicator to the current layer field 
Contributes to CURA-957
 2016-03-01 02:11:46 +01:00
Arjen Hiemstra
110c3fa754 Do not react to all Scene changes in LayerView but just childrenChanged 
When the layer data is updated, a new node is attached to the scene
root. We can thus watch for only children changes since everything else
can be ignored.

Contributes to CURA-938
 2016-03-01 02:11:46 +01:00
Arjen Hiemstra
f2d98cfba3 Do not show a message when processing top layers but rather leave it up to QML 
Contributes to CURA-957
 2016-03-01 02:11:46 +01:00
Arjen Hiemstra
c684e96ef1 Expose the new busy property to QML 
Contributes to CURA-957
 2016-03-01 02:11:46 +01:00
Arjen Hiemstra
e0afc1535a Add a busy property to LayerView that indicates whether we are currently building top layers 
Contributes to CURA-957
 2016-03-01 02:11:46 +01:00
Jaime van Kessel
67d10ef0a2 UpdateTopLayer timer is now only triggered when max layers changes 
CURA-969
 2016-02-29 15:51:40 +01:00
Jaime van Kessel
00dcf339c8 Visibility of processing message is now correct when switching between views. 
CURA-971
 2016-02-29 15:11:13 +01:00