03-27-2025, 11:01 AM
The "Grid Size" setting in the text display settings is the size of the text used in the chord grid. The chord grid calculations are based solely on the number of cells specified along with the width of the screen - each cell is given the same width regardless of the content within it. This matches the chord pro specification (which was discussed in another forum thread). So if you have really long chords, they are going to overlap with other text unless you reduce the text size or specify fewer cells. The current implementation is correct and is not going to change. You should reduce the grid text size to fit your chords if this is a problem for you. I do apologize that a buggy implementation was in place for so long though - it took me a number of updates to work through all the reported issues and resolve things through discussions with itsme and other users.
As far as the issue tracker, I do refer back to it, but I already have months of things planned right now, and I use the issue tracker for my own internal tracking - not for users to report issues. Users should report issues here on the forum.
As far as your other requests, itsme already has requested significantly more settings for ChordPro files to control the behavior. I'm not going to use a configuration file like the main ChordPro application (I think that's a little too much for the casual user), but I will have a more involved settings screen with many more options, but this is also going to require significant changes (both to track all of that in the database, implement all the UI changes for the new settings, and to change the logic to account for the new settings).
Mike
As far as the issue tracker, I do refer back to it, but I already have months of things planned right now, and I use the issue tracker for my own internal tracking - not for users to report issues. Users should report issues here on the forum.
As far as your other requests, itsme already has requested significantly more settings for ChordPro files to control the behavior. I'm not going to use a configuration file like the main ChordPro application (I think that's a little too much for the casual user), but I will have a more involved settings screen with many more options, but this is also going to require significant changes (both to track all of that in the database, implement all the UI changes for the new settings, and to change the logic to account for the new settings).
Mike