Page 2 of 4
Posted: Sat Mar 31, 2007 8:50 am
Yes I know the code completion cache thing isn't good (at all). I want to rewrite it but I do not know how to go about doing so (this was taken from the original Dev-C++). You are VERY welcome to help me if you can (remember C++ is arguably the most complex and ambiguous programming language on earth, just imagine the meanings of a '<' in different contexts (if (a < b), template<typename x> class Something, static_cast<x>(y), functionCall<parameterType> (a) are just a few I can think of))
I was trying to implement one using C++ where I can use Boost.wave but that is still a works-in-progress.
P/s you can still get madException from http://madshi.net/madCollection.exe
Joel , my appologize
Posted: Sat Mar 31, 2007 9:21 am
Joel , I'm sorry for the mistake I'd make. You have already fix the bug of the first one I mentioned before .
I've download the latest version of wxDev-C++ , it's great.
The word "minht" in the previous topic I posted should be "might"
Posted: Sat Mar 31, 2007 10:09 am
It's all good.
Posted: Wed Apr 04, 2007 7:28 am
The new Version of WxDevCpp is really great, I like the feature to preselect CompilerSets in .template files !
But there is one thing that hopefully can be improved in the next version.
When I want to start a new project (Menu File->new->Project), it takes extremely long to open the Templates Dialog (round about 30 - 40 seconds)
I experimentally removed all .template files from templates directory and the dialog appeared immediately.
So I think it must have something to do with new Template File Format.
Posted: Wed Apr 04, 2007 11:19 am
Yes. If you have many templates it may take a while, this is because we have to iterate over each template to make sure the compiler set thing is correct and exists. I'm not sure if we can fix this though (maybe we can look at it, but I'm not sure)
Posted: Thu Apr 05, 2007 8:54 am
Would you please email the source code of the latest version of wxdev-c++ to me? Or the code completion cache generating part.I like to help.
My email : [email protected]
Posted: Thu Apr 05, 2007 9:05 am
Isn't the source available on sourceforges SVN?
Posted: Thu Apr 05, 2007 9:39 am
But,there is something wrong with my sourceforge account.I couldn't login via SVN.
Posted: Thu Apr 05, 2007 6:30 pm
tbreina wrote:I'm hoping that Joel will be able to post the executable and new wxWidgets devpaks to our devpak server soon.
Me too! An automatic webupdate instead of uninstall+reinstall+reconfigure would be great!
Posted: Fri Apr 06, 2007 9:44 am
I just uploaded the new files. Please check WebUpdate.
Posted: Fri Apr 06, 2007 11:41 am
new bugs in 6.10.2:
* SashPosition doesn't work correctly in WxSplitterWindow (whatever I will do in project, splitter is set on startup in the same place)
* no Rows in GridSizer
old bugs (6.10.2 and 6.10.1):
* no correct displaying 0x00 0xF2 Unicode char in wxListCtrl (there is displayed simply empty line instead of line with text with this char)
* when you will put displaying wxProgressDialog in OnSelected event for wxComboBox, very often wxComboBox is expanded over wxProgressDialog
* some other reported by other people in other threads
Posted: Fri Apr 06, 2007 12:38 pm
lowjoel wrote:I just uploaded the new files. Please check WebUpdate.
Many thanks, Joel! A couple of issues:
When updating to 6.10.2 webUpdate failed to restart wxDev-C++ after shutting it down, and on manual restart the main window title is still "wxDev-C++ 6.10.1". On re-checking webUpdate, the 6.10.2 package no longer appears in the list. Am I updated or not?
edit: from my current devcpp.cfg:
wxDev-C++ Stable Release=188.8.131.52
Also, webUpdate reported not found on the 6.10-2 templates package.
Posted: Sat Apr 07, 2007 11:43 am
Nope, I don't think you are updated. You may have to manually download the file. The old versions could not copy itself over itself (if you get what I mean, since the OS locks binaries in executions against writing).
I've fixed the devpak problem though.
Posted: Sat Apr 07, 2007 2:08 pm
Thanks again, Joel. A few lingering questions, though:
lowjoel wrote:the OS locks binaries in executions against writing
-Is it possible that WebUpdate inadvertently shut itself down when it killed the wxDev-C++ process so as to unlock the binaries?
-Why is it that WebUpdate doesn't list the 6.10.2 package any more? Also, WebUpdate's "installed" column is always blank, even though it's successfully updated all the wxwidgets devpaks.
Posted: Sat Apr 07, 2007 2:42 pm
a - Possible.
b - WebUpdate thinks that you installed 6.10-2 and thus doen't allow you to select it anymore.