Bert Wesarg wrote:

> 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

There is no need to change anything for these action routines (they
can't return values).  All what was in question is the calltips()
macro function.  Btw, the selection dialog depends on the tags
collisions preference setting (smart versus all).  If anything, I
don't understand why the setting 'all' destroys the language mode
constraint for tips.

> calltip():
>  * should return the calltipID, or zero on failure
Yes.
>  * should never popup a 'not-found'-calltip
Yes.
>  * should fail for more than one matching, ie no dialog

Yes, where the matching depends on the smart or all behaviour, that
is, if the setting is smart, even if there are more than one matches
it may be possible to determine one, and then this one is shown.
That's the way it is now.  What should change is the dialog thing 
in case a single key can't be determined. In this case, no dialog,
return 0.

>  * a new mode for tips which don't fallback to tags

Yes, the "tipKey" mode should be changed such that it doesn't fall
back to "tagKey".  I think, if I want to show a tip and act according
to whether it is found or not, I don't want to find a tag, and if so I
can achieve this easily by repeating the lookup with "tagKey" in case
of a failure - that's what macro programming can do.  There is no need
for the simple one size fits all approach provided by the action
routines.

> Is this correct and are other developers with this? If, I have a look
> at this issue.

Can't we have a maintenance release first;-) and thereafter a switch
from CVS to subversion?  I know, coding surely is more fun, but IMO
the foundation for the changes to come is still missing somehow. 

Jörg
--
NEdit Develop mailing list - [email protected]
http://www.nedit.org/mailman/listinfo/develop

Reply via email to