Author Topic: Feedback on Code::Blocks  (Read 13154 times)

Offline Gena01

  • Multiple posting newcomer
  • *
  • Posts: 10
Feedback on Code::Blocks
« on: July 23, 2006, 03:11:54 am »
Hi. it's been a while since I looked at Code::Blocks. I am currently using MingwStudio  and thought I'd try to do the same stuff with Code::Blocks. 

I installed July 21,2006 nightly build.

Here are some things I noticed:
1. When Code::Blocks starts up with blank workspace "Project" menu has all the items enabled, but none of them do anything?. (MingwStudio actually has Create and Open items under Project menu)
2. Left Clicking or Right Clicking on the "Workspace" icon does not produce any popup menus or shortcuts.
3. You can save a workspace (which I would guess could contain multiple projects), but there's no recent workspaces menu item. And doing File->Open you get a filter for All Files (*.*)
4. If I have a file open for editing inside Code::Blocks and then I go and update that same file from outside of Code::Blocks, then Code::Blocks doesn't prompt me to reload the file. So if I continue to edit and save my file again it will override whatever changes were made outside of the IDE to the same file(s).
5. I setup win32.hlp as my help file inside Code::Blocks.  One nice feature that MingwStudio has is that I can be editing source code. And if i have mu cursor under SendMessage and if I press F1 then it opens up help on the topic of SendMessage. This way I can easily lookup any word within the help file by using F1.
6. If I hide the "build log" window and I do compile/build then it doesn't show it again unless I press F2. Is it possible to add an option to automatically show the "Build Log" when I am compiling something?
7.  If I have some warnings in my code and I press Ctrl+F9 then I can see my warnings in the "Build Messages". However if I press F9 the warnings are removed and not shown at all. (and my exe file is executed)
8. I am using GNU CC compiler. And some compiler options are missing from the lists (these are the ones MingwStudio also has) :
  - Enable Standard compiler warnings (-W) option is actually "Extra Warnings (-W)" in MingwStudio
  - Warnings, as errors (-Werror) would be nice to see on that list too..
9. It would be nice to see a version control plugin integrated into Code::Blocks. Having SVN directly in the IDE would be awesome.
10. Would be nice to have a "Release Unicode" and "Debug Unicode" targets available when creating new GUI or DLL projects for windows, but I can clone and setup those things myself for my projects.
11. Would be nice to have an import option for MingwStudio projects for people who are using that IDE.

These are just some of the things that I noticed. I think Code::Blocks is a great IDE that's growing and has a lot of potential. 

Gena01

Offline kidmosey

  • Multiple posting newcomer
  • *
  • Posts: 95
    • MUSITU International
Re: Feedback on Code::Blocks
« Reply #1 on: July 23, 2006, 04:58:35 am »
1. When Code::Blocks starts up with blank workspace "Project" menu has all the items enabled, but none of them do anything?. (MingwStudio actually has Create and Open items under Project menu)

At least it doesn't crash, eh? ;)

2. Left Clicking or Right Clicking on the "Workspace" icon does not produce any popup menus or shortcuts.

What should it bring up?  I think it lacks a context menu to avoid redundancy.  116 different ways to add a project to a workspace is only going to be more confusing, not more convenient.

3. You can save a workspace (which I would guess could contain multiple projects), but there's no recent workspaces menu item. And doing File->Open you get a filter for All Files (*.*)

Recent workspaces are saved under "Recent Projects". I don't know why.

4. If I have a file open for editing inside Code::Blocks and then I go and update that same file from outside of Code::Blocks, then Code::Blocks doesn't prompt me to reload the file. So if I continue to edit and save my file again it will override whatever changes were made outside of the IDE to the same file(s).

Settings->Environment->General Settings: "Check for externally modified files" (it works for me)

5. I setup win32.hlp as my help file inside Code::Blocks.  One nice feature that MingwStudio has is that I can be editing source code. And if i have mu cursor under SendMessage and if I press F1 then it opens up help on the topic of SendMessage. This way I can easily lookup any word within the help file by using F1.

That would be convenient, but for now the help plugin has a context menu.  Right click the word, then go to "Locate In" and select the help file to search.

6. If I hide the "build log" window and I do compile/build then it doesn't show it again unless I press F2. Is it possible to add an option to automatically show the "Build Log" when I am compiling something?

Settings->Environment->View: "Auto-hide message pane"  All relevant options should be here.

7.  If I have some warnings in my code and I press Ctrl+F9 then I can see my warnings in the "Build Messages". However if I press F9 the warnings are removed and not shown at all. (and my exe file is executed)

F9 is build and run.  Build and Run are two different steps; so, since the messages are cleared for each step, you only get to see the results of the Run step.  By what you wrote, you may have already realized this.  I am not aware of a way to keep the messages from being cleared or to save them.  I just build the project instead of Build & Run; then after I check the messages, I will (Build &)Run.

8. I am using GNU CC compiler. And some compiler options are missing from the lists (these are the ones MingwStudio also has) :
  - Enable Standard compiler warnings (-W) option is actually "Extra Warnings (-W)" in MingwStudio
  - Warnings, as errors (-Werror) would be nice to see on that list too..

You can still add -Werror under the "Other Options" tab, but I agree it would be more convenient to have it as a compiler option in the warnings checklist.

9. It would be nice to see a version control plugin integrated into Code::Blocks. Having SVN directly in the IDE would be awesome.

I thought they were working on that.  It was causing a horrible crash on RC2, though (it says on the download page).

10. Would be nice to have a "Release Unicode" and "Debug Unicode" targets available when creating new GUI or DLL projects for windows, but I can clone and setup those things myself for my projects.

Should only be a matter of learning wizard scripting (don't expect me to recommend wizards EVER again ;)).  This seems like something that could benefit all C::B users, though.

11. Would be nice to have an import option for MingwStudio projects for people who are using that IDE.

Don't know how familiar anyone here is with MingwStudio (I've never heard of it).


Well, I hope I was at least *some* help here.  I'm still relatively new to C::B. :D
« Last Edit: July 23, 2006, 05:00:54 am by kidmosey »
3 years until google knows more than god.

Offline takeshi miya

  • Lives here!
  • ****
  • Posts: 1487
Re: Feedback on Code::Blocks
« Reply #2 on: July 23, 2006, 02:34:45 pm »
2. Left Clicking or Right Clicking on the "Workspace" icon does not produce any popup menus or shortcuts.

What should it bring up?  I think it lacks a context menu to avoid redundancy.  116 different ways to add a project to a workspace is only going to be more confusing, not more convenient.
I don't think it lacks a context menu to avoid redundancy. It lacks because it has not been done yet.
And every IDE I know from the context menu let's you do:
* New Project
* Add Existing Project
* New Workspace
* Save Workspace
* Some other things

So it will be more confusing not having them. This is common behaviour.

5. I setup win32.hlp as my help file inside Code::Blocks.  One nice feature that MingwStudio has is that I can be editing source code. And if i have mu cursor under SendMessage and if I press F1 then it opens up help on the topic of SendMessage. This way I can easily lookup any word within the help file by using F1.

That would be convenient, but for now the help plugin has a context menu.  Right click the word, then go to "Locate In" and select the help file to search.
You can do exactly the same with the Help Plugin:
Go to Settings->Environment->Help files and choose "This is the default help file (shortcut: F1)". :)

Offline Gena01

  • Multiple posting newcomer
  • *
  • Posts: 10
Re: Feedback on Code::Blocks
« Reply #3 on: July 23, 2006, 02:42:03 pm »
5. I setup win32.hlp as my help file inside Code::Blocks.  One nice feature that MingwStudio has is that I can be editing source code. And if i have mu cursor under SendMessage and if I press F1 then it opens up help on the topic of SendMessage. This way I can easily lookup any word within the help file by using F1.

That would be convenient, but for now the help plugin has a context menu.  Right click the word, then go to "Locate In" and select the help file to search.
You can do exactly the same with the Help Plugin:
Go to Settings->Environment->Help files and choose "This is the default help file (shortcut: F1)". :)


But I did set it up as my default help file. It doesn't do lookups like "Lookup In" does..

Gena01

Offline Ceniza

  • Developer
  • Lives here!
  • *****
  • Posts: 1442
    • CenizaSOFT
Re: Feedback on Code::Blocks
« Reply #4 on: July 23, 2006, 06:43:59 pm »
Right, it does NOT do keyword lookup when pressing F1.

It's the second time I see someone expecting that behavior... I should add it :)

Offline takeshi miya

  • Lives here!
  • ****
  • Posts: 1487
Re: Feedback on Code::Blocks
« Reply #5 on: July 23, 2006, 11:53:40 pm »
Right, it does NOT do keyword lookup when pressing F1.

It's the second time I see someone expecting that behavior... I should add it :)

Hmm, bad memory from another program. :P
Yes, it's the expected behaviour after all. :)

Offline kidmosey

  • Multiple posting newcomer
  • *
  • Posts: 95
    • MUSITU International
Re: Feedback on Code::Blocks
« Reply #6 on: July 24, 2006, 03:53:03 am »
It's the second time I see someone expecting that behavior... I should add it :)

How about this?  Needs to check if a keyword exists, I think, but I don't know how to do that.
3 years until google knows more than god.

Offline Ceniza

  • Developer
  • Lives here!
  • *****
  • Posts: 1442
    • CenizaSOFT
Re: Feedback on Code::Blocks
« Reply #7 on: July 24, 2006, 04:53:35 am »
Thanks for the patch kidmosey but my solution to get that behavior was just to remove code and share the event IDs and Bind to one function only :)

I just hope people don't start asking for removal of that now :D

BTW, I've noticed a weird behavior in that plugin but I've been unable to find the right way to reproduce it, but it happens sometimes: playing with the configuration dialog, adding, moving up and down the F1 association changes to another file. Has anyone else noticed it?

Offline kidmosey

  • Multiple posting newcomer
  • *
  • Posts: 95
    • MUSITU International
Re: Feedback on Code::Blocks
« Reply #8 on: July 24, 2006, 07:31:53 am »
BTW, I've noticed a weird behavior in that plugin but I've been unable to find the right way to reproduce it, but it happens sometimes: playing with the configuration dialog, adding, moving up and down the F1 association changes to another file. Has anyone else noticed it?

Add a new entry with an empty location.
Set it as default.
Click OK.
Return to the config menu and the entry is missing.  Any entry you add will now become the default entry.  This has all sorts of nice effects whenever you move the entry up/down in the list before clicking OK. 

Guessing this has something to do with the save method saving all entries, or the load method not loading empty entries.
3 years until google knows more than god.

Offline Ceniza

  • Developer
  • Lives here!
  • *****
  • Posts: 1442
    • CenizaSOFT
Re: Feedback on Code::Blocks
« Reply #9 on: July 24, 2006, 07:41:06 am »
kidmosey: that one looks nice enough... but the thing is: I'ven't set any other entry to be the default one and it changes. I wonder if it has anything to do with empty locations too...

Offline kidmosey

  • Multiple posting newcomer
  • *
  • Posts: 95
    • MUSITU International
Re: Feedback on Code::Blocks
« Reply #10 on: July 24, 2006, 09:35:43 am »
Ceniza, it could.  If you create an empty location and move it in front of your default, when you reopen (or maybe if you just save) the configuration, it will set the next entry after your default as the new default (I think).

I haven't been able to find another way to do it, yet.

EDIT:
This seems to fix it, at any rate.
Code: [Select]
help_common.cpp: line 53
+    else if (m_DefaultHelpIndex >= count)
+        m_DefaultHelpIndex--;
« Last Edit: July 24, 2006, 09:49:59 am by kidmosey »
3 years until google knows more than god.

Offline Gena01

  • Multiple posting newcomer
  • *
  • Posts: 10
Re: Feedback on Code::Blocks
« Reply #11 on: July 24, 2006, 06:18:10 pm »
Thank you for fixing the help plugin to do word lookups. (haven't downloaded todays build yet, but I saw it in the changelog). Should I open Feature Requests regarding the right click menus and "Project" menu not working when there's only a blank workspace?

P.S. Is there a help file for Code::Blocks? Is one being worked on?

Gena01

Offline Gena01

  • Multiple posting newcomer
  • *
  • Posts: 10
Re: Feedback on Code::Blocks
« Reply #12 on: July 24, 2006, 06:19:56 pm »
7.  If I have some warnings in my code and I press Ctrl+F9 then I can see my warnings in the "Build Messages". However if I press F9 the warnings are removed and not shown at all. (and my exe file is executed)
8. I am using GNU CC compiler. And some compiler options are missing from the lists (these are the ones MingwStudio also has) :
  - Enable Standard compiler warnings (-W) option is actually "Extra Warnings (-W)" in MingwStudio
  - Warnings, as errors (-Werror) would be nice to see on that list too..
9. It would be nice to see a version control plugin integrated into Code::Blocks. Having SVN directly in the IDE would be awesome.
10. Would be nice to have a "Release Unicode" and "Debug Unicode" targets available when creating new GUI or DLL projects for windows, but I can clone and setup those things myself for my projects.
11. Would be nice to have an import option for MingwStudio projects for people who are using that IDE.

Also what about these items?

Thank you

Gena01

Offline kidmosey

  • Multiple posting newcomer
  • *
  • Posts: 95
    • MUSITU International
Re: Feedback on Code::Blocks
« Reply #13 on: July 24, 2006, 06:48:42 pm »
7.  If I have some warnings in my code and I press Ctrl+F9 then I can see my warnings in the "Build Messages". However if I press F9 the warnings are removed and not shown at all. (and my exe file is executed)

What functionality do you want here?  Do you want an option to save your message buffer between builds or do you want it to not reset between build and run?

10. Would be nice to have a "Release Unicode" and "Debug Unicode" targets available when creating new GUI or DLL projects for windows, but I can clone and setup those things myself for my projects.

I was thinking about this one... You think instead of two new wizards it could be possible to just include a "Unicode" checkbox in nearly every wizard?  It seems that would make for less clutter/wizards.
« Last Edit: July 24, 2006, 06:52:21 pm by kidmosey »
3 years until google knows more than god.

Offline Gena01

  • Multiple posting newcomer
  • *
  • Posts: 10
Re: Feedback on Code::Blocks
« Reply #14 on: July 24, 2006, 08:14:57 pm »
7.  If I have some warnings in my code and I press Ctrl+F9 then I can see my warnings in the "Build Messages". However if I press F9 the warnings are removed and not shown at all. (and my exe file is executed)

What functionality do you want here?  Do you want an option to save your message buffer between builds or do you want it to not reset between build and run?

Well I would suggest to make things consistent. And for me that would be the same behavior when I press F9 or Ctrl+F9 in terms of warnings and messages.

Gena01

Offline Gena01

  • Multiple posting newcomer
  • *
  • Posts: 10
Re: Feedback on Code::Blocks
« Reply #15 on: July 24, 2006, 11:33:41 pm »
Ok. I just installed July 24 nightly on a different computer. Thank you so much for adding the F1 lookup feature. It rocks. :)


And now I am seeing some more things:
12. In my default layout the "Compiler Toolbar" is too short... it's chopping things off at the word "buil"... so I don't get to see the rest of that toolbar and no way to resize or customize it...  (and yes I know it should say build and have dropdown options...) I tried to remove CodeBlocks files in my profile... that didn't help. Any way to fix this? should I need to look for some file to edit/remove? this is not happening on another PC...
13. I went into settings and disabled 80x80 icons... so now in settings I only see text. now the problem is that when I open any of the setting dialogs the first item on the left is not selected. (should be easy to fix this?)
14. If I select File->Open the default is "AngelScript" files (and remove the config files from Application Data\CodeBlocks ) ?
15. Same thing happens if I select "default workspace" instead of blank workspace...

Gena01

sethjackson

  • Guest
Re: Feedback on Code::Blocks
« Reply #16 on: July 24, 2006, 11:41:06 pm »
Ok. I just installed July 24 nightly on a different computer. Thank you so much for adding the F1 lookup feature. It rocks. :)


And now I am seeing some more things:
12. In my default layout the "Compiler Toolbar" is too short... it's chopping things off at the word "buil"... so I don't get to see the rest of that toolbar and no way to resize or customize it...  (and yes I know it should say build and have dropdown options...) I tried to remove CodeBlocks files in my profile... that didn't help. Any way to fix this? should I need to look for some file to edit/remove? this is not happening on another PC...
13. I went into settings and disabled 80x80 icons... so now in settings I only see text. now the problem is that when I open any of the setting dialogs the first item on the left is not selected. (should be easy to fix this?)
14. If I select File->Open the default is "AngelScript" files (and remove the config files from Application Data\CodeBlocks ) ?
15. Same thing happens if I select "default workspace" instead of blank workspace...

Gena01

12. It's a bug: http://developer.berlios.de/bugs/?func=detailbug&bug_id=6666&group_id=5358
13. Hmm yea shouldn't be too hard to fix.
14 and 15. Uhh not sure what you mean....  :?
« Last Edit: July 24, 2006, 11:46:32 pm by sethjackson »

Offline Gena01

  • Multiple posting newcomer
  • *
  • Posts: 10
Re: Feedback on Code::Blocks
« Reply #17 on: July 25, 2006, 12:53:43 am »
Ok. I just installed July 24 nightly on a different computer. Thank you so much for adding the F1 lookup feature. It rocks. :)


And now I am seeing some more things:
12. In my default layout the "Compiler Toolbar" is too short... it's chopping things off at the word "buil"... so I don't get to see the rest of that toolbar and no way to resize or customize it...  (and yes I know it should say build and have dropdown options...) I tried to remove CodeBlocks files in my profile... that didn't help. Any way to fix this? should I need to look for some file to edit/remove? this is not happening on another PC...
13. I went into settings and disabled 80x80 icons... so now in settings I only see text. now the problem is that when I open any of the setting dialogs the first item on the left is not selected. (should be easy to fix this?)
14. If I select File->Open the default is "AngelScript" files (and remove the config files from Application Data\CodeBlocks ) ?
15. Same thing happens if I select "default workspace" instead of blank workspace...

Gena01

12. It's a bug: http://developer.berlios.de/bugs/?func=detailbug&bug_id=6666&group_id=5358
13. Hmm yea shouldn't be too hard to fix.
14 and 15. Uhh not sure what you mean....  :?

regarding 14 and 15.. it seems like it remembers the last index of opened file type... in the "Open" dialog... so you need to delete the config files... or move them out of the way to reproduce this.. the files are stored in C:\Documents and Settings\<your_user_name_here>\Application Data\CodeBlocks

I just deleted the 2 files and opened up Code::Blocks. Code::Blocks starts with default settings. Now if I do File->Open the "files of type" says "AngelScript" which is the first option dropdown... If I select another option and open the project file then the next time I start Code::Blocks it uses the last selected option.

Gena01

sethjackson

  • Guest
Re: Feedback on Code::Blocks
« Reply #18 on: July 25, 2006, 01:09:02 am »
Ok. I just installed July 24 nightly on a different computer. Thank you so much for adding the F1 lookup feature. It rocks. :)


And now I am seeing some more things:
12. In my default layout the "Compiler Toolbar" is too short... it's chopping things off at the word "buil"... so I don't get to see the rest of that toolbar and no way to resize or customize it...  (and yes I know it should say build and have dropdown options...) I tried to remove CodeBlocks files in my profile... that didn't help. Any way to fix this? should I need to look for some file to edit/remove? this is not happening on another PC...
13. I went into settings and disabled 80x80 icons... so now in settings I only see text. now the problem is that when I open any of the setting dialogs the first item on the left is not selected. (should be easy to fix this?)
14. If I select File->Open the default is "AngelScript" files (and remove the config files from Application Data\CodeBlocks ) ?
15. Same thing happens if I select "default workspace" instead of blank workspace...

Gena01

12. It's a bug: http://developer.berlios.de/bugs/?func=detailbug&bug_id=6666&group_id=5358
13. Hmm yea shouldn't be too hard to fix.
14 and 15. Uhh not sure what you mean....  :?

regarding 14 and 15.. it seems like it remembers the last index of opened file type... in the "Open" dialog... so you need to delete the config files... or move them out of the way to reproduce this.. the files are stored in C:\Documents and Settings\<your_user_name_here>\Application Data\CodeBlocks

I just deleted the 2 files and opened up Code::Blocks. Code::Blocks starts with default settings. Now if I do File->Open the "files of type" says "AngelScript" which is the first option dropdown... If I select another option and open the project file then the next time I start Code::Blocks it uses the last selected option.

Gena01

Right the "Open" dialog remembers your last selection. This is on purpose. How is this a problem? Or maybe I just don't understand.....

Offline Gena01

  • Multiple posting newcomer
  • *
  • Posts: 10
Re: Feedback on Code::Blocks
« Reply #19 on: July 25, 2006, 03:19:06 am »
The problem is that I think it should not start with "AngelScript" as the starting point, but should have something like CodeBlocks project.

Gena01

sethjackson

  • Guest
Re: Feedback on Code::Blocks
« Reply #20 on: July 25, 2006, 03:20:25 am »
The problem is that I think it should not start with "AngelScript" as the starting point, but should have something like CodeBlocks project.

Gena01

Aha I see now. I agree. :)

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: Feedback on Code::Blocks
« Reply #21 on: July 25, 2006, 09:11:17 am »
The problem is that I think it should not start with "AngelScript" as the starting point, but should have something like CodeBlocks project.
It will do once you have selected something different. Your las selection is saved and applied next time you use the dialog.
With regards, Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

sethjackson

  • Guest
Re: Feedback on Code::Blocks
« Reply #22 on: July 25, 2006, 01:29:29 pm »
The problem is that I think it should not start with "AngelScript" as the starting point, but should have something like CodeBlocks project.
It will do once you have selected something different. Your las selection is saved and applied next time you use the dialog.
With regards, Morten.

Right. However I think it should start on something different. Like C++ source, or Code::Blocks project or something....

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: Feedback on Code::Blocks
« Reply #23 on: July 25, 2006, 01:39:50 pm »
Right. However I think it should start on something different. Like C++ source, or Code::Blocks project or something....
Well, we can only do it wrong: If we change to C then Anglescript (and C::B workspace/project) devs will complain. If we change to [whatever] the "other ones" will complain. Thus the strategy was to keep in mind the last selection which will most likely fit the dev's needs.
In addition: The extension list can change quickly if support for another set of files is added. And - in fact - this will happen with the new compiler framework. So this index we are settings there would have to be "maintained". I don't think that's a good idea. Thus - why not keeping it at the "first extension" only for the very first time?
With regards, Morten.
« Last Edit: July 25, 2006, 01:41:23 pm by MortenMacFly »
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

sethjackson

  • Guest
Re: Feedback on Code::Blocks
« Reply #24 on: July 25, 2006, 01:41:24 pm »
Right. However I think it should start on something different. Like C++ source, or Code::Blocks project or something....
Well, we can only do it wrong: If we change to C then Anglescript (and C::B workspace/project) devs will complain. If we change to [whatever] the "other ones" will complain. Thus the strategy was to keep in mind the last selection which will most likely fit the dev's needs.
In addition: The extension list can change quickly if support for another set of files is added. And - in fact - this will happen with the new compiler framework. So this index we are settings there would have to be "maintained". I don't think that's a good idea. Thus - why not keeping it at the "first extension"?
With regards, Morten.

Ok that makes sense. :)

Offline kidmosey

  • Multiple posting newcomer
  • *
  • Posts: 95
    • MUSITU International
Re: Feedback on Code::Blocks
« Reply #25 on: July 25, 2006, 02:17:17 pm »
In addition: The extension list can change quickly if support for another set of files is added. And - in fact - this will happen with the new compiler framework. So this index we are settings there would have to be "maintained". I don't think that's a good idea. Thus - why not keeping it at the "first extension" only for the very first time?

If you add an extension, would that not also possibly change the index value?  Why not save the extension instead of the index?
3 years until google knows more than god.

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5195
Re: Feedback on Code::Blocks
« Reply #26 on: July 25, 2006, 05:04:04 pm »
Quote
If you add an extension, would that not also possibly change the index value?  Why not save the extension instead of the index?
that's how it should be done !!!

Offline Gena01

  • Multiple posting newcomer
  • *
  • Posts: 10
Re: Feedback on Code::Blocks
« Reply #27 on: July 25, 2006, 05:26:39 pm »
From the whole discussion I see three possible issues:
1. The default starting index is 0 (AngelScript).
2. When I select "Open an existing project" link from the  "Start Here" (blank workspace) it should select the index to match CodeProject project files and not what was last used.
3. Index is used and saved across sessions. (and not extension?)

Gena01

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5195
Re: Feedback on Code::Blocks
« Reply #28 on: July 25, 2006, 05:29:02 pm »
I remember I once fixed some bugs so that the last extension was remembered (for generic open) bu I vae the impression something happened to it, since it does not work that well anymore ;-)

When opening project, it indeed should be cbp extensions selected, I will fix this.

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: Feedback on Code::Blocks
« Reply #29 on: July 25, 2006, 06:18:35 pm »
I remember I once fixed some bugs so that the last extension was remembered (for generic open)
Don't worry: It still works very well. That's what I'm saying: The last filter selection IS stored as name, not the index. Then from the name the index is being computed. If there is no name stored, the default index (which is zero) is used. Anyway, for the file-open dialog you have to come to an (integer) index in the end allthough you save the filter as literal (again: as it is done).

So in the end it only happens the very first time that you are presented the AngelScript filter because this has index zero (the default). I could only imagine doing in MainFrame::OnFileOpen(wxCommandEvent& event) not a int StoredIndex = 0; but something like int StoredIndex = GetDefaultFilterIndex(); which would resolve to what?
There are so many good reason to resolve to any of the following:
- C::B workspace
- C::B projects
- C/C++ source/header files
(...)
But again I'm saying: We don't know what a good default value is. If we set iot to "something" next time people will complain different.

The only thing I could imagine to have the default index set to "All files" which is always appended to the filter index list. This is already returned by FileFilters::GetIndexForFilterAll(). How about that?

With regards, Morten.
« Last Edit: July 25, 2006, 06:24:13 pm by MortenMacFly »
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline Gena01

  • Multiple posting newcomer
  • *
  • Posts: 10
Re: Feedback on Code::Blocks
« Reply #30 on: July 25, 2006, 06:50:35 pm »
Well another possible solution would be something that Microsoft did in Visual Studio. They have an Open menu that has a submenu. it has 2 options "Project/Solution..." and "File...". These two options have different sets of filters that they show. For Code::Blocks that could be project/workspace for the first and the other what's there now would be the second.

Gena01

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: Feedback on Code::Blocks
« Reply #31 on: July 25, 2006, 06:52:53 pm »
Well another possible solution would be something that Microsoft did in Visual Studio.
I'll look into this once I'm back at work (I've VS there). Anyway, I've submitted a patch that "All files" is selected as default filter index until a selection has been made which is then set as default.
I hope this satisfies user's needs better than "AngelScript"... so we are one step further... ;-)
With regards, Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ