Code::Blocks Forums

User forums => Nightly builds => Topic started by: killerbot on January 11, 2006, 12:20:12 am

Title: The 10 January 2006 build is out.
Post by: killerbot on January 11, 2006, 12:20:12 am
Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml
A link to the unicode windows wxWidget dll for Code::Blocks : http://download.berlios.de/codeblocks/wxmsw26u_gcc_cb.7z

The 10 January 2006 build is out.
  - Windows : http://download.berlios.de/codeblocks/CB_10jan2006_rev1707_win32.7z
  - Linux : not supported yet


Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 10 January 2006 build is out.
Post by: 280Z28 on January 11, 2006, 12:23:43 am
What do you mean by "# toolbar-images-not-changing-state (is a wx problem)"
Title: Re: The 10 January 2006 build is out.
Post by: killerbot on January 11, 2006, 12:25:33 am
It was artoj who asked me this to add to the list, and I remember a little bit seeing some discussions in other topics about this. I don't know 100% the problem.

@artoj : could you please explain again the problem
Title: Re: The 10 January 2006 build is out.
Post by: 280Z28 on January 11, 2006, 12:28:20 am
It was artoj who asked me this to add to the list, and I remember a little bit seeing some discussions in other topics about this. I don't know 100% the problem.

@artoj : could you please explain again the problem

If it has to do with the fact that the Abort button on the debugger toolbar doesn't go gray when it's disabled.... omg I tried to make that work but dang...
Title: Re: The 10 January 2006 build is out.
Post by: Michael on January 11, 2006, 10:26:08 am
It was not what was discussed here (http://forums.codeblocks.org/index.php?topic=1916.msg14823#msg14823)?

Michael
Title: Re: The 10 January 2006 build is out.
Post by: artoj on January 11, 2006, 11:45:05 am
It was not what was discussed here (http://forums.codeblocks.org/index.php?topic=1916.msg14823#msg14823)?

Yup, that's the one.

The affected buttons are (at least): save, print, find, replace and abort debug.

save - image always enabled
print - image always disabled
find - image always enabled
replace - image always enabled
abort debug - image always enabled

-----------

Could someone with proper rights to the SF.net project page close these bugs because they are now fixed:

1401383 (http://sourceforge.net/tracker/index.php?func=detail&aid=1401383&group_id=126998&atid=707416) 
1401376 (http://sourceforge.net/tracker/index.php?func=detail&aid=1401376&group_id=126998&atid=707416)

Thanks for killerbot for creating the patches (and devs for applying them). :)
Title: Re: The 10 January 2006 build is out.
Post by: artoj on January 11, 2006, 04:15:14 pm
I've posted the following bug to the tracker:

Quote
1. Launch Code::Blocks.
2. Create new project (File -> New project...)
3. Select Console application (or other project type). Select "C:\" (or other drive root directory) as the directory where to create files. Type name for the project.
4. Press OK. The project creation fails.

 #1403023 Project creation to drive root fails (nightly) (https://sourceforge.net/tracker/index.php?func=detail&aid=1403023&group_id=126998&atid=707416)
Title: Re: The 10 January 2006 build is out.
Post by: artoj on January 11, 2006, 05:01:03 pm
And next:

Quote
1. Open CodeBlocks and create new file (File -> New).
2. Minimize CodeBlocks.
3. Open the new file in external editor (such as Notepad).
4. Edit the file in Notepad and save changes you made.
5. Press the CodeBlocks button in the Taskbar to maximize CodeBlocks.
6. The file is changed but no reload file dialog is shown.

 #1403064 File modifications outside CB -notification fails (nighly) (https://sourceforge.net/tracker/index.php?func=detail&aid=1403064&group_id=126998&atid=707416)
Title: Re: The 10 January 2006 build is out.
Post by: thomas on January 11, 2006, 05:15:25 pm
I can confirm the bug in the 1717 build which I use to work with (fully optimized, stripped).

However, I was NOT able to reproduce it in the non-optimized, non-stripped 1717 build.  :?
Title: Re: The 10 January 2006 build is out.
Post by: artoj on January 11, 2006, 05:22:49 pm
I can confirm the bug in the 1717 build which I use to work with (fully optimized, stripped).

However, I was NOT able to reproduce it in the non-optimized, non-stripped 1717 build.  :?

Hmm...

@killerbot, what build flags do you use in the nightly builds?
Title: Re: The 10 January 2006 build is out.
Post by: killerbot on January 11, 2006, 05:42:59 pm
I use the cbp files, so that means several of them have debug info, non optimized, and during the update phase the debug info get's stripped off.
Title: Re: The 10 January 2006 build is out.
Post by: Michael on January 11, 2006, 05:54:17 pm
I have remarked another small issue (or may be it is just my crazy notebook :)).

When I select some text and I wish to move it, the arrow with the small rectangle appears, but when I click to put the text in the new position, it does not work :?. So, I have to press "Esc" to re-use C::B.

Has someone else remarked this problem?

Michael

[EDIT]: It seems it was just a local problem (i.e., my crazy notebook strikes again :)). After a new re-start, it works. Anyway, I have remarked that it do not put the text exactly where I would like, but just a line above :?.
Title: Re: The 10 January 2006 build is out.
Post by: artoj on January 11, 2006, 06:30:38 pm
I use the cbp files, so that means several of them have debug info, non optimized, and during the update phase the debug info get's stripped off.

OK, thanks.

So I can produce the bug with non-optimized build.

When I select some text and I wish to move it, the arrow with the small rectangle appears, but when I click to put the text in the new position, it does not work :?. So, I have to press "Esc" to re-use C::B.

Has someone else remarked this problem?

Sorry, I can't reproduce it. :(
Title: Re: The 10 January 2006 build is out.
Post by: Michael on January 11, 2006, 06:32:33 pm
When I select some text and I wish to move it, the arrow with the small rectangle appears, but when I click to put the text in the new position, it does not work :?. So, I have to press "Esc" to re-use C::B.

Has someone else remarked this problem?

Sorry, I can't reproduce it. :(

Sorry, just my fault :oops:. See my EDIT above.

Michael
Title: Re: The 10 January 2006 build is out.
Post by: artoj on January 11, 2006, 08:31:42 pm
OK, I have found another bug (it's bit hard to reproduce, it needs quick mouse hand)

1. Launch Code::Blocks and load the default layout (I'm using the default default layout, nothing changed).
2. Drag the management window so it will undock.
3. Dock the management window again to its default place.
4. Minimize Code::Blocks.
5. When Code::Blocks is minimizing quickly press the Code::Blocks taskbar button. You have to hit it before Code::Blocks is fully minimized. If you did it right Code::Blocks will be unrestoreable from the taskbar by pressing the taskbar button (you can actually restore it by right clicking the taskbar icon with mouse and selecting Restore).

This unrestoreable state only happens if you move the docking windows around.
Title: Re: The 10 January 2006 build is out.
Post by: thomas on January 12, 2006, 09:10:37 pm
And next:

1. Open CodeBlocks and create new file (File -> New).
2. Minimize CodeBlocks.
3. Open the new file in external editor (such as Notepad).
4. Edit the file in Notepad and save changes you made.
5. Press the CodeBlocks button in the Taskbar to maximize CodeBlocks.
6. The file is changed but no reload file dialog is shown.
Regarding this bug, I suggest you have "check for external modifications" turned off. It works without any problems here...

By the way, this is not a good place to post bugs.
Title: Re: The 10 January 2006 build is out.
Post by: artoj on January 12, 2006, 09:27:04 pm
Regarding this bug, I suggest you have "check for external modifications" turned off. It works without any problems here...

Hmm... try minimizing Code::Blocks by clicking the taskbar icon (in step 2.). I can reproduce this bug. The reload file dialog *is* shown after I minimize C::B again.

Quote
By the way, this is not a good place to post bugs.

I haven't posted it to SF.net yet because you said you cannot reproduce it.
Title: Re: The 10 January 2006 build is out.
Post by: thomas on January 12, 2006, 09:33:38 pm
Hmm... try minimizing Code::Blocks by clicking the taskbar icon (in step 2.). I can reproduce this bug. The reload file dialog *is* shown after I minimize C::B again.
That is an entirely different thing than what you wrote above. You said no dialog was shown at all. Now it is about the same dialog being shown over and over again.
My revision 1717 build does not show either of these bugs.
Title: Re: The 10 January 2006 build is out.
Post by: artoj on January 12, 2006, 09:52:05 pm
That is an entirely different thing than what you wrote above. You said no dialog was shown at all.

Yeah, you are right, I should have been more clearer. Partly this was because of the bug though, because the reload file pops up in wrong place I didn't notice it earlier.

After step 6. the reload file dialog is not shown. It isn't under the main application. It doesn't exist. Now, if I *after* step 6. minimize C::B the reload file pops up when C::B is fully minimized.
Title: Re: The 10 January 2006 build is out.
Post by: artoj on January 12, 2006, 10:36:41 pm
Here's the final set of steps:

1. Open CodeBlocks and create new file (File -> New).
2. Minimize CodeBlocks using taskbar icon. If you minimize using the minimize button in the top of the window the bug cannot be reproduced.
3. Open the new file in external editor (such as Notepad).
4. Edit the file in Notepad and save changes you made.
5. Press the CodeBlocks button in the Taskbar to maximize CodeBlocks. Do not restore by right clicking with mouse and selecting Restore.
6. The file is changed but no reload file dialog is shown.

Now try to regain focus to the main application (first lose the focus and then set the focus back) and the reload file dialog is displayed. This can be done e.g. by minimizing C::B.

If it's still unclear what I'm talking about, watch this flash demo, it shows the steps and reproduces the bug: http://ajonsson.kapsi.fi/pub/bug.htm (http://ajonsson.kapsi.fi/pub/bug.htm). It's made with Wink (http://www.debugmode.com/wink/). I know the colors look like s***t but I needed to keep the file size small. Now I'm going to bed. Good night.
Title: Re: The 10 January 2006 build is out.
Post by: killerbot on January 13, 2006, 12:37:45 am
I've posted the following bug to the tracker:

Quote
1. Launch Code::Blocks.
2. Create new project (File -> New project...)
3. Select Console application (or other project type). Select "C:\" (or other drive root directory) as the directory where to create files. Type name for the project.
4. Press OK. The project creation fails.

 #1403023 Project creation to drive root fails (nightly) (https://sourceforge.net/tracker/index.php?func=detail&aid=1403023&group_id=126998&atid=707416)

I have fixed this and posted a patch for it @ sourceforge.
@Yiannis, I have assigned it to you. Very little changes.
While debugging and fixing this I noted that the wxString's are not shown correctly when they contain a '\', it shows 2 characters for it , the '\' followed by another one.

Cheers,
Lieven