User forums > Nightly builds
The 27 October 2014 build (10016) is out.
Alpha:
@jens, less work is generally better; go ahead and commit.
Jenna:
--- Quote from: Alpha on November 07, 2014, 04:15:26 pm ---@jens, less work is generally better; go ahead and commit.
--- End quote ---
In svn (r10029).
I build the new revision and try to upload it, but it might not be possible before monday, because my provider will switch internet off this night (don't know the exact time) and I will not have any internet access until monday (at least).
wab:
I found a tiny bug, or non finished functionality.
Settings -> Compiler... -> Global Compiler Settings -> Other Settings -> Advanced Options... -> Commands:
1. Add new "Source ext.": ui
2. Field "Command" stay on "Compile single file to object file"
3. "Command line macro": $(#qt5.uic) -o "Src/GeneratedFiles/ui_$file_name.h" "$file"
4. "Generated files (to be further compiled)": Src/GeneratedFiles/ui_$file_name.h
So, when I'm add "Src/Kreator/somefile.ui" to project and make rebuild then:
a. File is generated inside right path: Src/GeneratedFiles/ui_somefile.h
b. CodeBlocks always put fixed position of "Auto-generated" path in window "Management -> Projects" to: "Src/Kreator/ui_somefile.h"
c. Because my ui_somefile.h is into "Src/GeneratedFiles/ui_somefile.h" - compiler cannot find it
(First solution) For working well I need to change:
ch.3. "Command line macro": $(#qt5.uic) -o "ui_$file_name.h" "$file"
ch.4. "Generated files (to be further compiled)": ui_$file_name.h
(Second solution) Or for alternative working well solution I need to change:
ch.3. "Command line macro": $(#qt5.uic) -o "Src\Kreator\ui_$file_name.h" "$file"
ch.4. "Generated files (to be further compiled)": Src\Kreator\ui_$file_name.h
But it is really mess when I have all generated files into main folder (first solution) or in folder of my source file Src\Kreator\* (second solution).
Auto-generated files for new extensions always put same directory as source. So first solution shouldn't work at all, but it work well :-).
So either I cannot configure this Code::Blocks functionality or it doesn't work like it should.
oBFusCATed:
--- Quote from: ollydbg on November 02, 2014, 03:04:17 pm ---Debugged a while, I found the reason why this bug happens, but I don't have a clean way to fix this issue.
See, the CC setting was stored in configure file.
When C::B start up, CC will create a default parser object called "temp parser".
When a parser object is created, it will copy the settings(such as the "Case sensitive matches") from the configure file to its own member variable.
When you open the CC dialog, the active parser object's setting will be modified also the CC related setting in configure files will get updated. This means, the configure file contains the active parser's settings.
When a CB project loaded, a new parser object(we call "new parser" here) is created and activated. So far, so good. When you changed the CC setting, both the "new parser"'s setting and the configure file get updated.
The issue comes when you close C::B, which means, you need to
1, destroy "new parser"
2, destroy "temp parser"
When destroy "new parser", all its setting was saved, but after that, the active parser switches to "temp parser", the setting in "temp parser" was active, and finally the "temp parser" get destroyed, its setting was saved (not the "new parser"), so your setting was lost!
I have not a good idea to fix this issue. Say, we have a setting shared by several parser objects. But they may be different, but the last destroyed parser's setting will be saved to the configure file.
--- End quote ---
Any plans to fix this issue? If not please say so, so I can take a look at it ... it is quite annoying...
ToApolytoXaos:
Apologies if I have asked again in the past: is it possible to add the same feature Find declaration... with Ctrl+mouse hover hotkeys?
I use NetBeans a lot for web development (Java as well) and find this feature quite appealing; it helps tremendously while looking for certain information about a class or member function.
How difficult is it to implement it?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version