User forums > Nightly builds
The 21 July 2012 build (8150) is out.
stefanos_:
Guys, can someone tell me if line 29 from include\cbplugin.h is correct? Should not be named PLUGIN_IMPORT?
As it is right now makes no sense to me I'm afraid...
--- Code: ---#ifdef __WXMSW__
#ifndef PLUGIN_EXPORT
#ifdef EXPORT_LIB
#define PLUGIN_EXPORT __declspec (dllexport)
#else // !EXPORT_LIB
#ifdef BUILDING_PLUGIN
#define PLUGIN_EXPORT __declspec (dllexport)
#else // !BUILDING_PLUGIN
#define PLUGIN_EXPORT __declspec (dllimport)
#endif // BUILDING_PLUGIN
#endif // EXPORT_LIB
#endif // PLUGIN_EXPORT
#else
#define PLUGIN_EXPORT
#endif
--- End code ---
Also, this link clear things up a bit about what is dllimport and what is dllexport. http://msdn.microsoft.com/en-us/library/81h27t8c(v=vs.80).aspx
ptDev:
--- Quote from: stefanos_ on July 25, 2012, 07:58:14 am ---Guys, can someone tell me if line 29 from include\cbplugin.h is correct? Should not be named PLUGIN_IMPORT?
As it is right now makes no sense to me I'm afraid...
--- Code: ---#ifdef __WXMSW__
#ifndef PLUGIN_EXPORT
#ifdef EXPORT_LIB
#define PLUGIN_EXPORT __declspec (dllexport)
#else // !EXPORT_LIB
#ifdef BUILDING_PLUGIN
#define PLUGIN_EXPORT __declspec (dllexport)
#else // !BUILDING_PLUGIN
#define PLUGIN_EXPORT __declspec (dllimport)
#endif // BUILDING_PLUGIN
#endif // EXPORT_LIB
#endif // PLUGIN_EXPORT
#else
#define PLUGIN_EXPORT
#endif
--- End code ---
Also, this link clear things up a bit about what is dllimport and what is dllexport. http://msdn.microsoft.com/en-us/library/81h27t8c(v=vs.80).aspx
--- End quote ---
It looks like the intention was to define PLUGIN_EXPORT as dllexport if either of EXPORT_LIB or BUILDING_PLUGIN is defined.
PLUGIN_EXPORT was a poor choice of macro name (something like CB_PLUGIN_API would have been better imho).
That arrowhead certainly could be simplified.
MortenMacFly:
--- Quote from: stefanos_ on July 25, 2012, 07:58:14 am ---Guys, can someone tell me if line 29 from include\cbplugin.h is correct? Should not be named PLUGIN_IMPORT?
--- End quote ---
It is correct. You control basically if the plugin (or declared methods) export their signature. Notice the difference in both lines:
__declspec (dllexport)
and
__declspec (dllimport)
We want to have one macro to achieve both: exporting and importing. If it would have two different names this would not work.
chice:
in rev8150 windows version, many resources (eg: icons) are broken and can not be displayed correctly.
rev8086 is ok.
Alpha:
--- Quote from: Vuki on July 23, 2012, 09:28:25 am ---This change in lexer_cpp.xml:
--- Code: --- <Style name="Comment (normal)"
index="1,23"
fg="160,160,160"/>
--- End code ---
is causing problems. When i changed it back to the previous form:
--- Code: --- <Style name="Comment (normal)"
index="1"
fg="160,160,160"/>
--- End code ---
the highlighter works correctly. The added ",23" part borks the highlighter and causes it to select colors from wrong entries.
--- End quote ---
I think that this is probably the cause of the issue that some users are experiencing (the new wxSmith generated code highlighting is the only other lexer related change, and it can be disabled). My guess is that even though the new index is correct (for the most recent Scintilla update), Code::Blocks cannot correctly load previously saved user customized color schemes (likely because of the added index).
A possible solution would be for the affected users to manually search default.conf for the lexer related entries, modifying what seems appropriate,
or deleting/moving default.conf, and recreating the preferred color scheme.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version