Hello,

I tested the latest 0.9.29 snapshot (rev 29671) and I am missing the "Custom Program" creation in the dialog "Project/New Project/Create a new project"

Is this by design now, or is it configurable in the IDE?

Regards, Bernd.

There were two options which were almost the same, they were called Program and Custom Program, they were merged. So just use Program.

It was removed by design, because it was almost the same as 'Program' and you can configure any item to any other. For example you can you can use 'Program' and disable whatever IDE feature you don't need.

Mattias

sorry, I don't get it.

I would like to let the IDE create the extension .pas, when the new project is saved as it was with 0.9.24/28. How can I do this?

Regards, Bernd.

?
?

Bernd Mueller hat am 12. Mai 2011 um 15:00 geschrieben:

Create a new project of type "Program".
Press Ctrl-S to get the save dialog. The default is "project1.lpr". Change the filename and the extension to pas.
Click ok.

Mattias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20110512/20a49f12/attachment.html>

yes, thank you, this works. Perhaps the file type .pas could be added to the file type combobox in the save dialog.

Regards.

Bernd Mueller wrote

Perhaps the file type .pas could be added to the file type combobox in the save dialog.

I have created a patch months (maybe even over a year now) where the IDE has user defined File Dialog filters and file extensions. Usage is exactly for things like you mentioned. For reason beyond me that patch was not accepted, but it is still in the Mantis Bug Tracker. I still use that patch in my local copy of my IDE though.

Regards,
- Graeme -

?
?

Graeme Geldenhuys hat am 12. Mai 2011 um 17:12
geschrieben:

On 12/05/2011 15:34, Bernd Mueller wrote: > >? Perhaps the file type .pas could be added to > the file type combobox in the save dialog.?

I added a filter list.?
?

?

Yes, and it is a nice dialog.?
But as far as I remember it lacks the ability to update defaults. For example the file group "project" was extended from *.lpr to *.lpr;*.dpr. The patch stores the default values to the config file, but a good config file should only contain the non default values.?
Just an idea: Maybe instead of storing a simple list it can store the extensions for each standard item plus the list of custom items. ?

Mattias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20110512/3102fd18/attachment.html>

2011/5/12 Mattias Gaertner:

But as far as I remember it lacks the ability to update defaults.

Simply delete your custom file extensions file, and a new one is created with the latest defaults. Obviously it might be wise to backup your old one first, so you can merge customizations back in.

For example the file group "project" was extended from *.lpr to *.lpr;*.dpr. The patch stores the default values to the config file, but a good config file should only contain the non default values.

That would be that for a "project" I would always have the IDE defaults, which I might not want. In my case, that was exactly so. I don't create LCL based projects, but do use the Lazarus IDE. So my desired defaults are very different. Just what I wanted.

Just an idea: Maybe instead of storing a simple list it can store the extensions for each standard item plus the list of custom items.

This makes a relatively simply feature so much more complicated, with very little benefit for all the efforts required to implement it. As I described above, simply delete or backup your customization file and the IDE will create a new one for you with the latest defaults.

Not to mention... how often does the IDE defaults really chance... in the last 6 years, very little. So is what you describe really needed. The bottom line is, I wanted *new* defaults, hence the feature in the first place - I don't care much for what the IDE considered defaults once upon a time. My filters look very different now, but it suits my needs.

What everybody else proposed in the bug report comments, simply limited the features of what I implemented.

Well, for one config item this might be doable. But in general this is a bad solution.

Easy solution: If a user clears the extensions of an item it is not shown. Then the item has a non default value, which is saved and kept even when you upgrade.

Complicated?
You just need to add a simple array.
If I would have the time to maintain your extension I would do that.

Not to mention... how often does the IDE defaults really chance... in the last 6 years, very little. So is what you describe really needed.

There were some feature requests about adding a mechanism to register new file types.

Your patch is a good start.

Mattias