...forced to open the binary file in Notepad++ when I'd prefer to open it with Hex Workshop by default...
The point of text file is to be easly editable, like in, when you tas, now for binary files, unless you are eating binary from morning to night, you wont edit it so easly.
My main question is, why do you want to open the binary files anyway?
Its not like you gonna change easly the input with a hex editor, so im assuming its more like to make little changes, while with a text file (and notepad++) yeah it make some sence, it can reload the file on the fly and you can stop/restart your movie in the emu quickly after some changes.
Botom line, when you open the .tas and you see garbage you can close it, it wont be something youll heavly edit like you would with just text.
Now all my excuses if you are one of those talented guys reading/writing binary as easly as text, "we" (the casuals, the average ect...) arent capable of this
Edit: you could also just associate with the hex editor, then you would use the right click> open in notepad++ for text files (it work on any file type)
I assume it is possible to make a context menu item working on any file extension and parsing the data then make the right choice, with .NET and stuff like that, I really see little point in this tho.
One day, perhaps there will be perfect TAS editing tools that beat Notepad++ in every way, all embedded in the emulator. Until that day, people like myself are going to use Notepad++ to edit their text formatted files whenever it appears to be the most convenient option. There's no reason to over limit the user.
TAS Editor in fceux currently is that TAS editing tool so the real push should be to try to port that to other emulators.
One day, perhaps there will be perfect TAS editing tools that beat Notepad++ in every way, all embedded in the emulator. Until that day, people like myself are going to use Notepad++ to edit their text formatted files whenever it appears to be the most convenient option. There's no reason to over limit the user.
TAS Editor in fceux currently is that TAS editing tool so the real push should be to try to port that to other emulators.
It's a great tool, but I like using Notepad++ sometimes. I'm just quicker when working with text formats, at least for splicing stuff.
2.1.6 obsoletes notepad++. And the current view of taseditor's code makes it easily portable to anywhere. As I was said.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
2.1.6 obsoletes notepad++. And the current view of taseditor's code makes it easily portable to anywhere. As I was said.
Wait... do you mean it would be easily ported across systems or across emulators because if there is a way for me to get TAS Editor working other emulators than that would be amazing.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
No, feos got it too optimistic.
Since major part of TAS Editor is GUI, it won't be as easily portable as, say, an emulator core.
feos, by "portable" I meant that TAS Editor code is now mostly detached from FCEUX code, making it independent from emulator. It's still dependent from console input type and actual coding platform (Win API in this case), so porting it to, say, dotnet, definitely wouldn't be easy.
Yes I thought about my xml suggestion and it was probably kind of silly in retrospective. I haven't actually looked at the format, but I'm still for using extensions that already exist (that was my actual point), like .txt or maybe even .xls (another bad idea :D) or similar if it's tables. Use the extension depending on whatever it should be edited with for texty files. Binary files have unique formats, it makes sense to use custom extensions for them as they should usually tell you about the format the data is stored in it. It doesn't make so much sense for plain text files in my opinion. Use extensions according to the format of the data, not according to the use of the file. Maybe .input or .keytable or something like that if .txt is not an option (so they'd be filtered out by a file type selector). Almost everything's better than using the same extension imo.
We sure don't want to download a bunch of .tas files and then "try" opening them with Notepad to see if they are text or binary.
