Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Communication between plugins (abbreviations, codecompletion)
p2rkw:
--- Quote ---Does patch 2 include/supersede patch 1?
--- End quote ---
Yes, I made patch2 after patch 1.
Today, I realized that I generate patch in wrong directory, so I'm attaching corrected second patch ( it seems that first one is unnecessary ).
I don't have perrmisions to upload patch, can you do that?
edit: patch removed form this post
p2rkw:
I found serious bug :/ Dont apply those patches.
daniloz:
I've tested the patch and like it (haven't been hit by the serious bugs yet). Just an icon is missing now... ;)
--- Quote from: MortenMacFly on August 21, 2012, 06:34:07 am ---
--- Quote from: p2rkw on August 20, 2012, 10:31:03 pm ---If abbreviation keyword will be selected it macro will be automatically expanded.
--- End quote ---
This should therefore be a function of the abbreviations plugin and not code-completion. Thus, no plugin-plugin communication is needed. :)
--- End quote ---
I understand the idea of having no plugin-plugin communication. However, me too, I'd like to see the abbreviations in the same list as the code-completion suggestions, without having to remember a different shortcut for using the abbreviations.
Idea: do a framework to show completions and from this framework, we could have plugins providing the suggestions (words) with a callback to a function that "insert/execute" the suggestion. ;D
Alpha:
Word of caution: how do you plan resolve identifiers that are both keywords and abbreviations (ex. struct, class, and while)?
MortenMacFly:
--- Quote from: Alpha on August 22, 2012, 08:46:29 pm ---Word of caution: how do you plan resolve identifiers that are both keywords and abbreviations (ex. struct, class, and while)?
--- End quote ---
True. I still think it shouldn't be mixed. I am rather happy with having two shortcuts here - one for CC and one for abbrevs. Maybe thy should be bound more close together, like:
CTRL + SPACE for CC and
CTRL + SHIFT + SPACE for abbrevs or alike.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version