Hi,
On Sat, Mar 8, 2008 at 9:48 PM, Joerg Fischer <[EMAIL PROTECTED]> wrote:
> Bert Wesarg wrote:
>
> > if the tags/tips selection dialog comes into play: all hell break
> > loose. ie the returned value from calltip() is again meaningless.
>
> No, not really. In this case, calltip() returns 0 for failure. As I
> admitted in an earlier post, I didn't address the behaviour of the
> calltip() function doing things on its own, which a real fix should
> do. That is, neither should the calltip() function pop up not found
> messages, nor pop up any dialogs for multiple tips/tags nor should
> "tipText" fall back to tags. This makes all sense for the show_tip()
> menu action, but not for a macro function. Here, if either a single
> tip in "tipText" mode or a single tag in "tagText" mode can't be
> determined, calltip() should simply fail, return 0 and be silent.
>
> To achieve this, perhaps it is better to write extra functions,
> instead of using findDef and findAllMatches, even if it just means to
> make copies and to leave out some parts like the 'if (nMatches>1) {'
> part.
>
> (Btw, I rather would like to stick to the calltip idea, which is being
> small shortly displayed messages. Having multiple calltips in the
> window seems a bit too much for this.)
>
To summarize your proposed behavior:
show_tip()/find_definition():
* doesn't need to return anything, or at least success?
* should popup a 'not-found'-dialog or -calltip
* should open a selection dialog, for more than one matchings
calltip():
* should return the calltipID, or zero on failure
* should never popup a 'not-found'-calltip
* should fail for more than one matching, ie no dialog
* a new mode for tips which don't fallback to tags
Is this correct and are other developers with this? If, I have a look
at this issue.
Bert
> Cheers,
>
>
> Jörg
--
NEdit Develop mailing list - [email protected]
http://www.nedit.org/mailman/listinfo/develop