1. 18 Feb, 2013 2 commits
  2. 17 Feb, 2013 7 commits
  3. 13 Feb, 2013 1 commit
  4. 07 Feb, 2013 1 commit
  5. 08 Feb, 2013 1 commit
  6. 03 Feb, 2013 1 commit
  7. 02 Feb, 2013 2 commits
  8. 24 Jan, 2013 2 commits
  9. 23 Jan, 2013 4 commits
  10. 19 Jan, 2013 3 commits
  11. 20 Jan, 2013 1 commit
    • Christopher Olah's avatar
      Clean up the monitor command. · 3fb7a3e7
      Christopher Olah authored
      The monitor command now:
      
      * Has more pythonic code
      * Limits precision of progress elements (12.3% instead of 12.347812...%)
      * Uses a carriage return to have print progress replace the previous
        progress line.
      
      For example:
      
      Monitoring printer, use ^C to interrupt.
      Updating values every 5.000000 seconds.
      Print progress: 0.3%
      
      Previously, the line "Print progress: 0.3%" was "Print progress: 0.2%",
      etc.
      3fb7a3e7
  12. 19 Jan, 2013 1 commit
  13. 20 Jan, 2013 1 commit
    • Christopher Olah's avatar
      Fancy configurable prompts! · 29c97003
      Christopher Olah authored
      * Prompts are now generated based off of string templates,
        for example: "%(bold)sT:%(extruder_temp_fancy)s %(progress_fancy)s
        >%(normal)s "
      
      * We have a dictionary of prompt string templates for different
        situations.
      
      * We have bold support for the prompt.
      
      * We have extruder temperature support for the prompt.
      
      * We have progress support for the prompt.
      29c97003
  14. 15 Jan, 2013 1 commit
    • Miro Hrončok's avatar
      Tell the user, there was an error while connecting · f942c1a0
      Miro Hrončok authored
      Before, when there was an error while connecting, user didn't know, when
      Pronterface wasn't launched from the terminal.
      
      So you could just hit Connect button several times and all you've get was:
      Connecting...
      Connecting...
      Connecting...
      
      Now, when there is an exception during the connection, the user will notice:
      Connecting...
      Error: You are trying to connect to a non-exisiting port.
      
      Or:
      Connecting...
      Error: You don't have permission to open /dev/ttyUSB0.
      You might need to add yourself to the dialout group.
      
      Unfortunately pyserial's SerialException doesn't provide errno yet, so the
      message isn't so user friendly:
      Connecting...
      could not open port None: [Errno 2] No such file or directory: 'None'
      
      I've filled a bug report with patch to pyserial.
      
      Together with this I've realised, there is unnecessary UTF8 decoding of the
      output. When user has UTF-8 locale, there was an exception when printing the
      exception to the output (almost an exception inception). So I have dropped it,
      but feel free to add it back, if I broke anything else.
      f942c1a0
  15. 13 Jan, 2013 7 commits
  16. 12 Jan, 2013 5 commits