-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove the 6 year old TODO file #1964
Conversation
Agreed, but some of these are valid. We should probably file bug reports for those not currently represented in our tracker. This is a very timely process. I would recommend going line-by-line and crossing them out. People like @musikBear @Sti2nd @Umcaruje @mikobuntu @curlymorphic @badosu and myself could help with this effort, since they're very familiar with the state of our current tracker. -Tres |
You mean this one |
I will start by deleting the items i know are done.
|
@curlymorphic Thanks for going through the list! I edited your list into the PR description so that people can leave comments here just detailing the ones they know are safe to remove. @musikBear yes, that's the one. I can't make sense of very many of these. In regards to this entry:
I tried dragging both the vertical mixer channel bars and the FX slots in the FX chains, and neither of them support dragging. Any idea what this one is referring to? Maybe a feature of the old mixer? Is it safe to delete this entry? |
This seems to be referring to this piece of the code (replicated below): if( ConfigManager::inst()->value( "ui",
"compacttrackbuttons" ).toInt() )
{
setFixedSize( 32, 29 );
}
else
{
setFixedSize( 160, 29 );
}
setIconSize( QSize( 24, 24 ) ); So the ratio of the icon to the text is currently 85%-15% (24/160 is 15%). A ratio of 80%-20% could be achieved by |
I just tested that and it appears that this issue has since been solved; removing this item from the list. |
This hasn't been implemented & wasn't on the issue tracker, so I created #1983 for it. |
As far as This condition is detected in mfmidi.cpp:31. Following the call chain, the message isn't logged in that class, but is relayed to a pure-virtual method, Mf_error. The only class that implements that is Alg_midifile_reader in allegrosmfrd.cpp:172, which just logs the error to the console. Looking further, it looks like LMMS' MidiImport class doesn't bother using that Midi reader for some reason though (so you can probably discard the above information). The only call into the allegro library is, from what I can tell, in creating an So from what I can tell, no checks are made to ensure that a Midi file has > 0 tracks. Therefore this issue is probably still valid. But I don't know enough about Midi to be able to create a 0-track midi file and test it. |
This PR isn't needed since the TODO file was removed via #2210. @Wallacoloo if you'd like, feel free to reopen this as a bug report (or several, depending on your approach). |
The TODO file in the repository root hasn't been touched in 6 years. We have an issue tracker, so I don't see the need of keeping a to-do file in the actual repository anymore.
Edit: I'll maintain the entries of the to-do list that haven't been implemented / posted to the tracker below. Leave a comment on which ones are safe to be removed:
Unknown if valid or not:
Probably still valid issues for which no tracker exists: