[PATCH] Various updates to user manual

Miika Turkia miika.turkia at gmail.com
Mon Aug 4 01:47:44 PDT 2014


On Mon, Aug 4, 2014 at 11:08 AM, Willem Ferguson <
willemferguson at zoology.up.ac.za> wrote:

>  On 04/08/2014 07:00, Miika Turkia wrote:
>
>  On Thu, Jul 24, 2014 at 10:31 PM, Willem Ferguson <
> willemferguson at zoology.up.ac.za> wrote:
>
>>
>> N.B.:
>> The only outstanding issue that I am aware of, is the discussion last
>> week about including
>> depth and time pointers along the Y and X axes respectively when the
>> cursor is
>> moved about on the profile panel during manual profile creation. This was
>> true for V3 but has since
>> disappeared. I favour the inclusion of the pointers along the depth and
>> time axes.
>> Tomaz indicated that this could easily be done. Pending a final decision
>> on this issue
>> I might do a final modification or two to the text of the manual.
>>
>
>  What is the solution to this going to be? I created a bug 674 during the
> weekend to remind, that the user manual is currently not ready for release.
> It has to be updated regarding this feature, whether the X/Y pointers are
> enabled or not.
>
>  miika
>
>
> _______________________________________________
> subsurface mailing listsubsurface at hohndel.orghttp://lists.hohndel.org/cgi-bin/mailman/listinfo/subsurface
>
>  The manual can only be updated if pointers on the X and Y-axes are indeed
> implemented. Taking into account the intense activity over the last 10
> days, the problems with the Win support and the fact that Tomaz is
> obviously overloaded, I suggest that the issue about pointers on the dive
> profile stays over for V4.3. Its is a nice-to-have, not a blocker (and it
> should possibly go hand in hand with adjusting the way zooming is performed
> on the dive profile, as has been discussed a number of times). It just
> looks to me there are more important issues at the moment to get V4.2 out.
> I hope this sounds sensible?  :-)
>

I am happy either way, as long as the documentation matches the actual
functionality, or at least does not describe something that does not exist.
That is why I consider the current state a blocker...  Updating the
documentation not to mention the markers at all would be quite safe in any
case. It is not confusing to not describe that feature even if it exists,
but it sure is confusing if it is documented but missing.

miika
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hohndel.org/pipermail/subsurface/attachments/20140804/2be58e21/attachment.html>


More information about the subsurface mailing list