User forums > Nightly builds
The 19 september 2006 build is out.
artoj:
--- Quote from: Pecan on September 20, 2006, 04:01:38 pm ---I still cannot recreate the error(latest SVN). I click on codeSnippets/searchButton/Scope. The dot is there.
I then click on File/Open/cancel. I then click on Codesnippet/SearachButton/Scope. Again, the dot is there.
How do you create the error?
--- End quote ---
I just click on File and then on the Code Snippets' menu and the dot is gone. Your DPI settings are probably hiding the bug.
Someone had already reported the bug to the wxWidgets' bug list so I just added a comment, the bug number is #1542190. The bug has been on the queue for about a month now and none of the developers have commented it.
I also made a simple test application (binary / source). The binary version is linked against the monolithic dll (unicode).
In the test application first click the "Create a popup menu" button. Then click File menu to see the menu item with the image and then click "Create a popup menu" button again. On my system the popup menu appears larger and in the radio submenu the check mark is gone.
eckard_klotz:
Hello evrybody
This shoud be an answer for the question of killerbot to my posting in the topic " The 18 september 2006 build is out." where I described how to run C::B under winME.
killerbot wrote:
--- Quote ---could you try out a nightly , rc2 is very old.
In the nightly announcements there's very often a reply from setjackson providing a link to an ansi build (which is what you need on WinMe). It is possible there might be problems with that one also, not sure.
--- End quote ---
Sorry, I didn't make it clear (I know my English is not the best one): I started with rc1 and rc2 last year, but since end of july I'm trying to use the ansi-nightlies. The last ansi-nightly I tried out today, was the one from yesterday. It seams to work also, if I don't use the "debuggergdb.dll" ,allowing to run more than one instance and disabling the loading of any file while stating.
Perhaps you have more details you want to know or you wish to ask me to do some experimental things. Don't hasitate to do so, but perhaps it may take one or two day before I can answer.
Kind Regards,
Eckard Klotz.
griffin2000:
As recommended in another thread I upgraded to this build... I get the following issues:
I get no filename or line for warnings of errors in the build message window (it worked fine in RC2): e.g:
For this message in the build log:
c:/p4_perforce.z-axis.com1666_gmorgans/AGT/Internal/Tools/TestBed\.\\source/modules/TestLoopListModule.cpp:53: warning: invalid access to non-static data member 'ObjectSingle::mNode' of NULL object
I get this message with not line or file in the build message window:
warning: invalid access to non-static data member 'ObjectSingle::mNode' of NULL object
I've tried changing the build message regular expression and it makes not difference. The default expression is:
([ \tA-Za-z0-9_:+/\.-]+):([0-9]+):[ \t]([Ww]arning:[ \t].*)
I've tried changing it to this but it makes not difference:
(.+):([0-9]+):[ \t ][Ww]arning:([ \t ].*)
Its also seems to define $make as the the minGW make executable, not matter what you define your make program as in compiler options.
griffin2000:
And there is another strange difference... I have custom tool to do a perforce check-out on a file. In RC2 it would automatically recognise the file has changed and bring up "file has change, reload?.." dialog. But with this build it no longer does that, I have to close and re-open the file.
griffin2000:
--- Quote from: griffin2000 on September 20, 2006, 08:11:35 pm ---I've tried changing the build message regular expression and it makes not difference. The default expression is:
--- End quote ---
In fact if I copy the compiler output string to the "test" window it recognizes it fine.
Navigation
[0] Message Index
[*] Previous page
Go to full version