FIXED?: Missig Template for different files

[ScrKiddle]

In the Tool-Bar menu, there is a button to create new files.
There are many templates to quickly create some files of specific file-type.
Some file-types get offered, but they don not have a template and so this quick-menu does not work on them.
It is may better to exclude filetypes from the menu if there is no template, and by that the menu does nothing on such a specific filetype anyway.
Or at least to let the menu create just an empty file if there is no template.

Example:
ASM
CEval
Framescript
JavaScript
Lisp
MASM
MSSQL
rexx

[Rickard Johansson]

I don't understand what you mean, or the issue

Could you give an example?

(The new file dropdown menu is mostly used to create a file with a specified file extension, so you don't have to save the file with a name and extension for highlighting to work).

[ScrKiddle]

tools_menu_new_file_offers_inexistent_files.png (15.33 KiB) Viewed 389 times

Toolbar-Menu for new files.
It offers file-types, clicking one tile-type does offer a template or more, some entries do not have a template, clicking on such a "main-item" does not open the templates because they do not exist.

Example:

Code: Select all

...
Actionscript > .as
...

The menu-item "Actionscript" offers a template ".as", clicking the sub-item "-as" in "Actionstript will open a new empty Actionstript-file with extension "-as".

Other example:

Code: Select all

...
ASM >
...

The menu-item "ASM" offers no template, clicking the sub-item ".asm" in "ASM" ist not possible (as it does not exist), clicking the main-item "ASM* will do nothing (it is obsolet as long the user does not add some own template).

Expected:
If file-types are offered, they should have a template to create a new file of this type.
If there is no template to create a new file of this type, the file-type should not get offered in the "new"-menu, because its not possible to create the file of this type without a template.

[Rickard Johansson]

Thanks, I'll look into it.

[Rickard Johansson]

I think it's fixed now in next version. Thanks!