<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
So I've finally got a chance to look at my non-API calls. I was
able to code around most of them, but there are two that would be
much easier if we could make them APIs. (I haven't pushed any of
these changes to my git repo yet.) Could we consider making these
API?<br>
<ul>
<li>keybindings_load_keyfile - I dynamically add/remove a variable
number of plugin keybindings based on the plugin settings, so
this allows me to refresh the results easily. This allows my
external-tools plugin to have any number of tools with each
their own keybinding. Otherwise, most plugins have a set number
of bindings.</li>
<li>keybindings_lookup_item - I know keybindings_get_item is
available already, but I am attempting to look up a core group
keybinding and not plugin's own keybindings.<br>
</li>
<li>keybindings_dialog_show_prefs_scroll - I remember someone
saying the "Configure Plugins" window would have a button to
this already in a later version, but I still don't see it. I
only need this API if the button isn't added.<br>
</li>
</ul>
Let me know if this is possible or how I should proceed. I use
geany with my plugins daily, and can't upgrade my code base until my
plugins are working.<br>
<br>
Thanks,<br>
<br>
Steve<br>
<br>
<div class="moz-cite-prefix">On 05/29/2015 07:21 PM, Colomban
Wendling wrote:<br>
</div>
<blockquote cite="mid:55691087.4090401@herbesfolles.org" type="cite">
<pre wrap="">BTW, @Steven: search_find_text() is <b class="moz-txt-star"><span class="moz-txt-tag">*</span>NOT<span class="moz-txt-tag">*</span></b> part of the Geany plugin API
and never have been. The fact you can use it is a issue of the way
Geany API was exported, and it is fixed in the dev version (meaning it
won't work anymore).</pre>
</blockquote>
<br>
</body>
</html>