User forums > General (but related to Code::Blocks)
Feedback on Code::Blocks
sethjackson:
--- Quote from: Gena01 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
--- End quote ---
Aha I see now. I agree. :)
MortenMacFly:
--- Quote from: Gena01 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.
--- End quote ---
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.
sethjackson:
--- Quote from: MortenMacFly on July 25, 2006, 09:11:17 am ---
--- Quote from: Gena01 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.
--- End quote ---
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.
--- End quote ---
Right. However I think it should start on something different. Like C++ source, or Code::Blocks project or something....
MortenMacFly:
--- Quote from: sethjackson on July 25, 2006, 01:29:29 pm ---Right. However I think it should start on something different. Like C++ source, or Code::Blocks project or something....
--- End quote ---
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.
sethjackson:
--- Quote from: MortenMacFly on July 25, 2006, 01:39:50 pm ---
--- Quote from: sethjackson on July 25, 2006, 01:29:29 pm ---Right. However I think it should start on something different. Like C++ source, or Code::Blocks project or something....
--- End quote ---
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.
--- End quote ---
Ok that makes sense. :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version