1. 10 Jan, 2018 4 commits
    • Jasem Mutlaq's avatar
      Bump to 2.9.1 · abf0a115
      Jasem Mutlaq authored
      abf0a115
    • Jasem Mutlaq's avatar
      Update version and shortcuts documentation · d31601be
      Jasem Mutlaq authored
      d31601be
    • Jasem Mutlaq's avatar
      Update tab order · b0567db5
      Jasem Mutlaq authored
      b0567db5
    • Robert Lancaster's avatar
      Here are a few bug fixes that I did today that should fix a couple of annoying... · b91a103f
      Robert Lancaster authored
      Here are a few bug fixes that I did today that should fix a couple of annoying KStars issues, particularly on OS X, in preparation for the 2.9.0 release.
      
      1. I fixed a Window Update issue that shows up when we use QT 5.10.0 for KStars on Mac.  It only seemed to affect a couple of items, the Log, the Solution Table, and the Guider Disconnect Button.  Basically, I just issued a repaint command so that the window would update when it was supposed to do so.  If this gets fixed in the future, the repaint commands can be removed.
      2. There was an OS X issue with using QDialog for the parent class of Ekos.  It was auto-assigning a default button so that when the user would hit enter somewhere in Ekos, it would execute that button’s command.  This was particularly problematic if the user was editing a Text box and hits enter to enter the value.  I fixed it by disabling all push buttons in Ekos as being the auto default button.
      3. The keyboard shortcut for the AstroCalculator was Ctrl-C (on Mac, CMD-C), this was a problem because it would interfere with the user copying info from the log at the bottom of Ekos.
      4. The Middle progress indicator in the Summary screen was not getting updated if the user selected the camera in the guide module to be the same as the main camera.  This was a problem for PHD2 because the user might not actually be using an INDI camera at all.
      5. The Star Profile view was not getting updated if the user was using the Fitsviewer like it was in the other views.
      6. I deleted a debug statement and a previously needed band-aid for klauncher that seems to no longer be necessary.
      
      And a Bonus, now that we can build using QT 5.10.0, the Whats Interesting blank-screen bug will go away.
      b91a103f
  2. 09 Jan, 2018 1 commit
  3. 08 Jan, 2018 3 commits
    • Robert Lancaster's avatar
      I was doing more testing, and the range on the sliders needs to be expanded... · 928bb5bd
      Robert Lancaster authored
      I was doing more testing, and the range on the sliders needs to be expanded just slightly so that it includes all the data.
      928bb5bd
    • Jasem Mutlaq's avatar
      Bump INDI dependency to v1.6.1 · a55bfd0d
      Jasem Mutlaq authored
      a55bfd0d
    • Robert Lancaster's avatar
      In preparation for the OS X release of KStars 2.9.0, I hunted around for any... · 307c2225
      Robert Lancaster authored
      In preparation for the OS X release of KStars 2.9.0, I hunted around for any bugs I could find and I made several small changes.
      
      1. Set the size of the fitsviewer AFTER showing it.  This fixes a bug that showed up in QT 5.10
      2. Widened the fitsviewer just a little to show all buttons.
      3. Added a cutoff enabling button in the 3d Graph so that the cutoff is not enabled by default and this button toggles it on and off.
      4. Made the fitsviewer not immediately load the 3d Graph view before the user selects something to view.
      5. Fixed a minor error in the 3D graph zoom algorithm.
      6. Set the Star Detection Algorithm for the FITS_Normal and FITS_Align views so that the user can get a good HFR of the stars in the frame.
      307c2225
  4. 07 Jan, 2018 6 commits
  5. 06 Jan, 2018 2 commits
  6. 04 Jan, 2018 1 commit
    • Robert Lancaster's avatar
      This patch is for KStars. It will set the path in the environment variable... · 83498b91
      Robert Lancaster authored
      This patch is for KStars.  It will set the path in the environment variable for the DSI to function on Mac.  Second, I thought the environment variables were getting a little messy, so I wrote a function that would clean them up a bit and make it easier to add more.  And finally, I found a better way to get the QImage for the Star Profile plot using a copy of a portion of the main QImage that matches the tracking box instead of using the tracking box pixmap function.  This way the overlays will not be included and the image zoom will not affect the profile.  The x and z axes are now actually pixels.
      83498b91
  7. 02 Jan, 2018 3 commits
  8. 01 Jan, 2018 2 commits
  9. 31 Dec, 2017 2 commits
    • Robert Lancaster's avatar
      Just a few minor changes. · 660266ca
      Robert Lancaster authored
      1. I added more functions to the nonlinear spin box to make it easier for KStars to add new recommended value items and to get the list of recommended values.
      2. I made sure that in those new functions, it would not mess up the overall range of the spin box.  It will expand the range if the new recommended value is outside the current range but will not make the range smaller.
      3. I made sure that the recommended values are always sorted correctly.
      4. I changed the exposure spin box in the capture module to use the new functions.  This also ensures that 0 does not get added to the list if the min and the max do not get set from the current CCD.
      5. I made the guide module request the valid exposure values and set the spin box to those recommended values on equipment connection, and save the message so if the user tries to set it to an invalid value, it doesn’t have to ask PHD2 what the valid values are every time.
      660266ca
    • Robert Lancaster's avatar
      As I said, I would try to take care of the Dither issues with PHD2. This... · b991d240
      Robert Lancaster authored
      As I said, I would try to take care of the Dither issues with PHD2.  This patch should prevent the observed problems.
      
      1. It adds a Timer that will keep track of the amount of time since the dither request was initiated.  Then if PHD2 doesn’t respond within the dither timeout that it dithered, then either the capture sequence will continue or it will be aborted depending on whether the user selected ditherFailAbortsAutoGuide.
      2. It eliminates some of the dither messages I added when dithering wasn’t working so well.
      3. It adds a “Dither” label to the drift graph so that you know when dithering occurred.
      4. It prevents GuideSteps during the dither and settle time from being added to the drift Graph.
      5. It changes conditions of the dither failure after settle occurs so that if the user didn’t select that ditherFailAbortsAutoGuide it won’t abort the sequence
      
      CCMAIL:kstars-devel@kde.org
      b991d240
  10. 30 Dec, 2017 2 commits
    • Jasem Mutlaq's avatar
      Add min and max to the list · 064437e3
      Jasem Mutlaq authored
      064437e3
    • Robert Lancaster's avatar
      This patch does several things: · 43ecd47c
      Robert Lancaster authored
      1. Adds the NonLinearDoubleSpinBox class and makes both Capture Module and Guide Module use them with appropriate values (These can be changed).
      2. Handles displaying an error message when the PHD2 pixel scale is incorrect because the user didn’t enter equipment info in PHD2.
      3. Displays Connecting and disconnecting Messages for PHD2 and PHD2 equipment.
      4. Improves some of the Guiding/Settling/Dithering code so that it gives more feedback and might fail to dither less often.
      5. Adds the environment variable for the apogee camera firmware.
      43ecd47c
  11. 29 Dec, 2017 1 commit
    • Robert Lancaster's avatar
      This patch should do the following: · 8ba4cd3c
      Robert Lancaster authored
      PHD2 Changes:
      1.  Clean up PHD2 header file to match the skeleton of PHD2 methods like I did before for the cpp file
      2.  Removes the former connect/disconnect code and fits them into the request/response/event format of the rest of the PHD2 communications
      3.  The change above corrects some longstanding bugs with connecting, so I could remove the band-aid I put into the last patch.
      4.  Prevents the calibration success event from accidentally starting guiding when first connecting
      5.  Moves the request list removal stuff to the bottom of the cpp file so it is all together.
      6.  Removes requests that had errors now and handles some of them.
      7.  Simplifies the handling of the JSON objects so they ALL fit into either events, responses, or errors.
      8.  Adds a LOSTLOCK abortTimer so that it waits 5 seconds after the star lock is lost before aborting guiding, in case it is reacquired
      9.  Adds a list of GuideParamChanges but doesn’t implement them.
      10.  Pauses between requests from PHD2 so that it doesn’t get too many requests at once.
      11.  Adds the DE Guide Mode change communications between Ekos and PHD2.
      12. Adds the Set Exposure Method so Ekos can tell PHD2 how long of an exposure to set.
      13.  Disables the RA mode buttons and SWAP button for PHD2.
      8ba4cd3c
  12. 27 Dec, 2017 5 commits
    • Jasem Mutlaq's avatar
      ead1b81d
    • Jasem Mutlaq's avatar
      Initial work for adding a dome toolbar · b5363378
      Jasem Mutlaq authored
      b5363378
    • Jasem Mutlaq's avatar
      This patch should fix two bugs I found with PHD2. · 625721ef
      Jasem Mutlaq authored
      The first is that it would state “Calibration Completed” when it first connects even when PHD2 had not even started calibrating yet.  Basically when first told to guide, all guiders would  be told to calibrate and PHD2’s method would just emit that the calibration was successful then move on to guiding when the calibration would actually occur.  To solve this, I just prevent it from trying to calibrate PHD2 in the first place and just go straight to guiding, where PHD2 will automatically calibrate it.  Now it doesn’t print that the calibration is completed until it really is completed.
      
      The second is an issue with the situation where PHD2 is already guiding when KStars connects to it.  Multiple state commands are issued, that it is guiding, that it is connected, etc.  The issue was that the Guide button was being disabled because it was guiding, then enabled because the equipment was connected, and then it tried to disable it again because it was guiding but it couldn’t because the first time it did it the PI was set to animated.  So I disabled the lines of code that prevented the setBusy command from executing if the PI indicator is running, but only for PHD2.  Now the Guide button works correctly.
      
      I also deleted an unnecessary line of code from the patch I made yesterday that added the pulse graphs since the line above it already takes care of it.
      625721ef
    • Jasem Mutlaq's avatar
      + Fix issue with non-guide dithering blocking regular calibration. · 3b61f05d
      Jasem Mutlaq authored
      + Fix issue with non-guide dithering getting triggered while guiding.
      + Robert fixes for PHD2.
      3b61f05d
    • Jasem Mutlaq's avatar
      Fix small typo · 25abb45b
      Jasem Mutlaq authored
      25abb45b
  13. 26 Dec, 2017 1 commit
    • Robert Lancaster's avatar
      This patch should add the pulse graphs for RA and DEC with settings to turn... · 4e953461
      Robert Lancaster authored
      This patch should add the pulse graphs for RA and DEC with settings to turn them off.  It includes a slider to adjust the height of the corrections axis independently.  It also corrects the display of the RA error on the graph, which was upside down. It increases the amount of information that is saved when the guide data is exported.  And finally, it adds pulse data to the tooltip when any is available.
      
      This has been corrected for the former sign difficulties I believe.
      4e953461
  14. 24 Dec, 2017 1 commit
  15. 23 Dec, 2017 3 commits
  16. 22 Dec, 2017 3 commits