Bug #7089 2006-04-09 18:13

madrenegade

Bug in Breakpoint Window and Watch Window

Hi I think I have found 2 bugs...

1:

When You add breakpoints in a file and than delete the file you cannot delete the breakpoints. So they are always in the window where the breakpoints are listed...

2.

In the window which is opened when you click Add Watch the OK-Button is going away when you have too much watch variables defined but this is only the case when you add a lot off vars and then close the window and reopen it again... maybe it is a little bit confusing how i described this so if it is not clear what I mean I could give you some screenshots ;)

PS: Code::Blocks rocks ^^

Category
Application::Error
Group
 
Status
Closed
Close date
2006-07-06 17:57
Assigned to
 
ID_24639 2006-04-09 19:59

Uhh what OS version, and C::B version?

Try a nightly build from here.

http://forums.codeblocks.org/index.php?board=20.0

madrenegade 2006-04-10 05:04

I have WinXp SP2 an and the C::B Build from the 07 april 2006...

ID_24639 2006-05-03 15:51

Ok. Could you post some screenshots please?

I would host them on Imageshack.

http://imageshack.us

madrenegade 2006-05-03 16:11

ok at first all is ok

http://madrenegade.smithtec.de/pics/all_is_ok.JPG

when you add some breakpoints first all is ok

http://madrenegade.smithtec.de/pics/also_ok.JPG

but when you close the breakpoint-window now and open it again the ok and cancel button disappears

http://madrenegade.smithtec.de/pics/not_ok.JPG

ID_24639 2006-05-03 19:30

Well I found the problem. I don't know how to fix. The problem lies with the XRC resource...... A developer will have to fix this.

mandrav 2006-05-25 11:39

1. Right click on the breakpoints in the list and remove them.

mandrav 2006-07-06 17:57

Report is closed.

Note: This is a preformatted standard message.

Possible reasons for closing this report are:

* the developer in charge of the issue

- could not reproduce it despite trying several times

- did not get sufficient information

- got no reply to an inquiry for specific information

* the report is quite a bit dated of now, and

- no user comments have been added for several weeks

- significant changes have been made to the code

- no other developer could reproduce it either

It is assumed that the problem does not persist and the report

can be closed.

If the problem reappears in future releases, please feel free to

re-open this report and provide precise information on how to

reproduce it.