Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Expand Envvars Plugin to Compiler Executables Path

<< < (3/3)

scarphin:
Ok, thanks. I didn't get your point on 'per project files/folders to scan' though. Also can you please enlighten me about the constructor trick, what problems may arise if events are registered inside the constructor?

Btw any confirmation on the 'settings -> environment' bug?

MortenMacFly:

--- Quote from: scarphin on January 31, 2015, 03:15:02 pm ---what problems may arise if events are registered inside the constructor?

--- End quote ---
Ok - I've seen your patch. The bad thing is, that if you connect in the destructor the plugin will always receive notifications no matter if its enabled or not. So you would have to put a check whether or not the plugin is actually enabled nearly everywhere. So that probably not a good solution.

I think its really a design flag in the plugin system of C::B - we should have something like a weight for plugin to make sure you enabled them in the right order. So sorry, I don't see a better solution for you other than the one you have.


--- Quote from: scarphin on January 31, 2015, 03:15:02 pm ---Btw any confirmation on the 'settings -> environment' bug?

--- End quote ---
No I didn't try so far.


--- Quote from: scarphin on January 31, 2015, 03:15:02 pm ---I didn't get your point on 'per project files/folders to scan' though

--- End quote ---
if you have a project open, goto:
Project settings -> Tab "C/C++Parser" -> Add additional search paths here.

Navigation

[0] Message Index

[*] Previous page