There is an input field for the file name at the top. There's no restrictions, but it will normalize input before saving the file name to the tracker or .h file. We can back that sanitizing action up to user input if need be, but for now it'll just strip slashes and stuff before trying to add the song name as the file name in the download name or use it in the songName variables in the .h output.
The save / export buttons are disabled and grayed out unless you have a file name (loading a tracker file will look for a meta.name entry and if it's not there it'll use the file name itself). Hovering over the buttons while the field is empty will prompt the user for a song name. Once filled each button's tooltip will say what the file name is that the button action will save / export as.
There is an input field for the file name at the top. There's no restrictions, but it will normalize input before saving the file name to the tracker or .h file. We can back that sanitizing action up to user input if need be, but for now it'll just strip slashes and stuff before trying to add the song name as the file name in the download name or use it in the songName variables in the .h output.
The save / export buttons are disabled and grayed out unless you have a file name (loading a tracker file will look for a meta.name entry and if it's not there it'll use the file name itself). Hovering over the buttons while the field is empty will prompt the user for a song name. Once filled each button's tooltip will say what the file name is that the button action will save / export as.
This addresses issue: https://github.com/ModusCreateOrg/trackerEditor/issues/8