With this PR class tooltips would look like:

![geany_py_calltip_custom_class_original](https://user-images.githubusercontent.com/617017/202919909-22f90ee2-d9ff-4583-872e-b9ac4fba66b0.png)
![geany_py_calltip_custom_init](https://user-images.githubusercontent.com/617017/202919981-11d0d5b4-9ce1-4611-8f62-02fbdc14b803.png)
![geany_py_calltip_global_tag_class](https://user-images.githubusercontent.com/617017/202919984-e191eb0e-1d52-4282-a175-da5f19e0ef4b.png)

> also modifying the calltip code to show the class name instead of `__init__`.

after this it would look like:
![geany_py_calltip_custom_class](https://user-images.githubusercontent.com/617017/202919940-6e7d7aeb-0fd2-48aa-9f27-7111dfd16670.png)

Great idea.
The other variants keep the same.
If you agree, I'd commit that change.

There is still a difference: signatures created by ctags (also within Geany) 
list the "self" argument as part of the signature while it is missing from the 
generated tags file. Adding it to the generated tags file would be easy 
(probably).
But this raised the question if "self" should maybe dropped from the calltip 
for Python at all. This is another very Python specific thing: each method must 
accept a first argument, called "self" by convention, but this argument is 
never passed when calling the method.
So, the signature should contain the special argument while a calltip probably 
should omit it as you must not pass it when calling the method.

On the other hand, this would require even more Python specific code :(.
What do you guys think?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3334#issuecomment-1321212468
You are receiving this because you are subscribed to this thread.

Message ID: <geany/geany/pull/3334/[email protected]>

Reply via email to