You are here

Home

Update

Error message

  • Deprecated function: Return type of DatabaseStatementBase::execute($args = [], $options = []) should either be compatible with PDOStatement::execute(?array $params = null): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2244 of /home1/dhulse/public_html/_eqmac/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home1/dhulse/public_html/_eqmac/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home1/dhulse/public_html/_eqmac/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home1/dhulse/public_html/_eqmac/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home1/dhulse/public_html/_eqmac/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home1/dhulse/public_html/_eqmac/includes/database/database.inc).
  • Deprecated function: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in drupal_random_bytes() (line 2268 of /home1/dhulse/public_html/_eqmac/includes/bootstrap.inc).
  • Deprecated function: rtrim(): Passing null to parameter #1 ($string) of type string is deprecated in url() (line 2349 of /home1/dhulse/public_html/_eqmac/includes/common.inc).
  • Deprecated function: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in url_is_external() (line 2393 of /home1/dhulse/public_html/_eqmac/includes/common.inc).
  • Deprecated function: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in url_is_external() (line 2395 of /home1/dhulse/public_html/_eqmac/includes/common.inc).
  • Deprecated function: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in url() (line 2311 of /home1/dhulse/public_html/_eqmac/includes/common.inc).

Having completed most of the coding for the Mount Limits feature, I have decided that to integrate it in an excellent way (as opposed to a not so great way), it would be necessary to refactor some of the low-level mount driver routines. This has now been done, but it means that the rest of the software now needs to be reworked to use the newer low-level driver. This is taking some time and is the reason for the delay is releasing the Mount Limits feature. The added benefit of doing this rework is that I will finally be able to fix some long standing issues, such as not being able to correctly perform an emergency stop in the middle of a slew. In addition, the software should be more responsive and will allow concurrency between the axes. For example, when stopping both axes, the software had to wait for the RA axis to stop, then wait for the DEC axis. These type of things can now occur in parallel, which makes more sense because the mount hardware fundamentally supports this.
So, I just wanted to provide a brief update to let you know what is happening. I'm trying to work through the necessary changes, but I've also been busy at work lately, so it is taking longer than expected. For this reason, I wouldn't like to speculate about when I may be able to do the next release, but I really hope I will manage it soon. Since it is quite an extensive set of changes, I will probably move to v1.0.0 for the next release.