d6553a29c6
First throw at clustering of settings
2013-07-09 21:41:26 +02:00
31698d3543
First version of setup.py for packaging OctoPrint
2013-07-09 21:39:07 +02:00
9038bc2bcd
Cleaned up a bit in .gitignore
2013-07-09 21:37:14 +02:00
c33c32410b
Added configurable pause triggers to be able to react to custom firmware messages with pausing/unpausing/pause toggling
2013-07-08 18:01:10 +02:00
8dcbb620bb
Highlight currently selected file, disable deletion and load/loadAndPrint for it
...
Fixed #182
2013-07-07 23:27:22 +02:00
7d85860195
Reset view to first page in file lists when filters are changed
2013-07-07 14:18:08 +02:00
c9e261df32
Use absolute values for self._serial.timeout, not relative ones
...
Thanks to @spapadim for spotting this
2013-07-05 16:58:00 +02:00
6d3e3221b8
Added timeout settings for serial communiction, initial connection and baudrate detection
...
Closes #126
2013-07-04 21:26:53 +02:00
3ffaaa19be
Merge branch 'master' into devel
2013-07-01 15:26:00 +02:00
407c61cb24
Removed contents that are now found on the website, added note regarding filing bug reports
2013-07-01 15:23:40 +02:00
aa9d92417a
Removed peakZ again, doesn't work this way
...
Slicers might raise the print head first for a "nose dive" onto the print platform, leading to a high peakZ already dialed in, with no way to get it down again. This way events won't be fired until the print reaches the height of the initial starting point. As a z-change is a z-change if z changes, we'll just fire the event now (if oldZ != newZ). Event consumers will have to think of a way to filter out the noise.
(cherry picked from commit 9227bb5
2013-06-30 22:28:04 +02:00
e62578eb11
Reset peakZ on new print
...
(cherry picked from commit 83a864d
2013-06-30 22:27:43 +02:00
44f1f01001
Allow enabling of serial logging at runtime
2013-06-30 22:18:29 +02:00
f14acf8ba7
Fix height of terminal output to 340 px
2013-06-30 21:17:22 +02:00
119ee338f1
Client side filtering of M105 request/response and M27 request/response
...
Since it's client side, if you leave these on when not printing, the log will go completely blank over time due to filling up with M105s. Re-enabling M105s will immediately restore the whole log (although it won't hold much information value).
2013-06-30 21:10:09 +02:00
98d4317e6f
More error resilience
2013-06-30 21:01:35 +02:00
9227bb5fd0
Removed peakZ again, doesn't work this way
...
Slicers might raise the print head first for a "nose dive" onto the print platform, leading to a high peakZ already dialed in, with no way to get it down again. This way events won't be fired until the print reaches the height of the initial starting point. As a z-change is a z-change if z changes, we'll just fire the event now (if oldZ != newZ). Event consumers will have to think of a way to filter out the noise.
2013-06-30 19:15:16 +02:00
83a864d3d8
Reset peakZ on new print
2013-06-30 00:03:34 +02:00
81464d65b7
Some more cleanups
2013-06-29 23:48:27 +02:00
0ed8f0f28d
Fixed typo, better error handling.
2013-06-29 20:39:49 +02:00
42f2398ac1
Only auto-connect if configured port is available at server startup. Also bugfixes.
2013-06-29 20:28:37 +02:00
8231e70b44
Added tab in settings for serial connection options
2013-06-29 20:20:27 +02:00
b0518a71a3
Also provide access to the auto-connect setting in the connection and the settings dialog
2013-06-29 19:57:46 +02:00
30e1624127
Merge remote-tracking branch 'CapnBry/autoconnect' into devel
2013-06-29 19:16:10 +02:00
9607de7d17
Removed matchesGcode again since it's not needed anymore
2013-06-29 19:09:55 +02:00
a9c35e5cf9
Changed gcode regex slightly to be on the safe side (we don't want to accidentally capture comments etc)
2013-06-29 19:06:14 +02:00
5b976b5300
Merge branch 'devel' into CapnBry-sendperf
...
Conflicts:
octoprint/util/__init__.py
2013-06-29 18:38:23 +02:00
530cdcd26a
Some refactoring (grouping methods, extracting classes, etc)
2013-06-29 18:37:47 +02:00
747fc4acc4
More in-source documentation for events
2013-06-29 14:33:05 +02:00
5ee2b41bfa
Merge branch 'master' into devel
2013-06-29 14:32:40 +02:00
2992438249
Just in case something goes wrong during reading the git repo information...
...
(cherry picked from commit 04ce284
2013-06-29 13:46:22 +02:00
e2bfdfd10c
Added git information to website
...
(cherry picked from commit 1caba2d
2013-06-29 13:46:12 +02:00
04ce284085
Just in case something goes wrong during reading the git repo information...
2013-06-29 13:43:45 +02:00
1caba2d634
Added git information to website
2013-06-29 13:41:39 +02:00
eb565645eb
Remove profiling code
2013-06-28 14:19:35 -04:00
b9144c2edc
Microoptimization to not build the same string twice
2013-06-28 14:19:34 -04:00
cb30d1fdd0
Refactor send command gcode handlers into individual functions. Very little gain if any.
2013-06-28 14:19:34 -04:00
b1c5c58f02
Rename gfunc -> gcode
2013-06-28 14:19:34 -04:00
715eb142f8
gcodeToEvent can only fire one event per gcode function anyway. <1% performance increase.
2013-06-28 14:19:33 -04:00
b5661c6f5e
Remove unused comm logQueue. 18% performance increase (12% vs baseline)
2013-06-28 14:19:33 -04:00
905923cc4c
Switch ringbuffer lists for deques. 6% performance boost (4.5% vs baseline)
2013-06-28 14:19:33 -04:00
9dd754fdae
Remove matchesGcode and instead just parse the code once. 29% performance increase
2013-06-28 14:19:32 -04:00
1b45d15430
Merge branch 'master' into devel
...
Conflicts:
octoprint/util/comm.py
2013-06-27 21:51:09 +02:00
dd3e9030fa
Yet another fix for the M999 resend issue
...
Should hopefully now be also fixed in case of a newly established connection with the printer, which was a regression due to the fix of the resending code.
2013-06-27 21:12:06 +02:00
24bb0fdf05
Added missing return statement that caused an exception
2013-06-27 21:05:01 +02:00
b75a0ec5c3
Add a serial.autoconnect setting to connect to the printer on startup
2013-06-26 10:19:32 -04:00
8b384ef530
Small rewording
2013-06-25 22:00:52 +02:00
ae438ca03f
Fixed evaluation of "remember login" function
2013-06-25 20:09:40 +02:00
09ae8fcdc2
Always send M110 with the new line number (default 0)
...
Previously it worked since the first command of every print was forced to be an M110 and the line number at the beginning of each print was always forced back to 0 as well. Now it just uses the actual line number (increased on each sent of a checksumed/numbered line) and resets that when an M110 is encountered. What was missing was forcing the line number of the actual M110 command to the desired line number as well. Should be "more correct" than before now, and work.
2013-06-25 20:05:31 +02:00
c9fb4e1ded
Also send identity_changed event on passive login
...
(cherry picked from commit 695f3f3
2013-06-25 19:32:05 +02:00
Gina Häußge