removed tooltips from PR

I can't find code where docMessageis set to something meaningful or even used.
Basically docStatusis the only meaningful change.

Clicking on a table row emits signal currentItemChanged that calls slot itemChanged (texdocdialog.cpp, l. 25).
itemChanged clears the warning icon and message fields and calls delayedCheckDocAvailable with package name as an argument (l. 143). The called routine starts checkTimer (l. 188). On signal timeout slot checkDockAvailable is called (l. 23). There (l. 198ff) docStatus for the package is retrieved which is Undefined by default (s. class LatexPackageInfo), so help->texdocAvailableRequest is executed (else case see next section). This runs the texdoc cmd, after that texdocAvailableRequestFinished reports the result with signal texdocAvailableReply (help.cpp, l. 142, l. 173). Be aware that this signal sends a non empty (custom) message in a special case (l. 129). In any case the signal is catched in texdocdialog (l. 26) and calls slot updateDocAvailableInfo. Depending wether the texdoc for the package is available and the custom message the LatexPackageInfo is updated (l. 219, s. also class LatexPackageInfo) and the warning icon and message fields are set accordingly.

When a row is clicked for that the texdoc info has been stored previously in the package info, these information can be retrieved imediately and the warning icon and message fields are set accordingly (texdocdialog.cpp, l. 202f).

okay, so there are only two messages (texdoc not found.a and No Documentation Available.)
If texdoc is not available, the whole help mechanism does not work. Any reason to spend the effort with the docMessage ?

someone decided to have the option for a custom message. I didn't want to change this. But in principle it would suffice to store the available value and hard code the negative message. One hast just to see what should happen to the special case. Discuss about effort is useless, because code is finalized.

okay, I would prefer to have only the status stored.

the line help->texdocAvailableRequest(lastDocRequest); actually needs to return a false (unsuccesful) when texdoc is missing instead of a signal.
This would clarify the whole set up.

@sunderme but this means that the user doesn't receive a note when texdoc cmd is not set up.
Meanwhile I update the PR with your suggestion.

Thanks