Noting, of course, how the pattern 00 is used twice.
Then I want to create a copy (duplicating the patterns). I select all four frames in the Frame Editor, Copy, then Paste & Dupolicate, and I get something like this:
The difference is that while the source involved only three pattern IDs (00, 01, 03) the copy involves four (02, 04, 05, 06). I might instead expect to see something like this:
...where pattern 02 is used in two frames, just like its source (pattern 00) was.
On the other hand, I have personal disagreements about how FamiTracker assigns pattern IDs to new frames in the first place (I prefer non-repeated patterns to always have the same ID as the frame they appear in if possible) so it doesn't really make a difference to my workflow either way, I'm just wondering in principle which one is more "correct".
And, of course, this is something that only crops up when duplicating patterns from more than one frame simultaneously.
So this is the 20th request thread you've created since you signed up to the forums. Congratulations!
Tell me, are you trying to turn this piece of software into StratelierTracker? In any event, please accept this celebratory fanfare that I have created in a very short amount of time using this already very efficient tracker to commend you on this spectacular feat!
How is that ad hominem? He was criticizing your request by saying it was unnecessary by bringing up examples of your past actions and comparing them to the present.
In all seriousness, 'Lepage has a point. He has made QUITE A FEW request threads, as well as a few bug report threads that just seem REALLY nitpicky, and almost a little like he's looking for issues to point out.
As a game designer myself, if I had someone pointing out these things, I would welcome it gladly. jsr is certainly able to act on or ignore whatever he pleases, but he can't possibly catch every bug in his software.
Rest assured, if I had the proper apps set up to compile FamiTracker's code myself, I would just, shall we say, "stick a fork in it"....
The whole reason I even noticed this in the first place is because I have a song whose patterns proceed in a roughly A-B-A-D, E-F-E-G order from frame to frame. I wanted to add a second verse following it that is basically a remix of the first (i.e. it cannot just reuse those patterns), and the quickest way to do that is to highlight all frames, Copy, then Paste & Duplicate. In doing so, I noticed the repeating structure of the original is somewhat lost (not in terms of how the song actually plays, but in terms of the pattern IDs assigned to each frame).
In short, just because I want these patterns duplicated from the original does not necessarily mean I want them duplicated from each other in the process.
I can totally understand how it even happened: When you issue a Paste Duplicate command from a selection of multiple frames, FamiTracker duplicates them one frame at a time (thus if multiple frames use the same patterns you get multiple distinct duplicates). Maybe it should duplicate them one pattern ID at a time?
Did it impact my workflow? Sort of, but a larger impact is me disagreeing with how FamiTracker initializes pattern IDs on new frames, so the fact that I ended up having to cut & paste pattern data (while manually reassigning pattern IDs) was not affected in the slightest.
modusponens wrote:
As a game designer myself, if I had someone pointing out these things, I would welcome it gladly. jsr is certainly able to act on or ignore whatever he pleases, but he can't possibly catch every bug in his software.
It might be nice to have a dedicated bugtracker sometime -- something dedicated to the nitty gritty, which frees the forums up from that. You guys already know I belong to the "no bug too small" camp. And in a wiki environment, I'm more likely to make technical edits (spelling/grammar fixes, minor wording or structural tweaks, etc.) than anything else. That's apparently just how I roll.
There's nothing wrong with noticing small bugs and telling them to the developer, but the problem is that you're making tons of barely useful threads that are clogging up the forum. If you'd make this thread a "super tiny bugs"-thread, you'd stop clogging up the forum. This thread could be designated to those things, and everytime you or someone else find a new one, you just post it here. Isn't that a much better idea?
No objections to that. In fact, jsr used to maintain a general buglist thread per each version release, but seemed to stop doing that around 0.4.4 or so.
I guess this request makes sense, it was something that was overlooked while adding the duplicate feature.
You could also use the merge duplicated patterns after pasting, but that would affect all frames which might be undesired.
Stratelier wrote:
It might be nice to have a dedicated bugtracker sometime -- something dedicated to the nitty gritty, which frees the forums up from that. You guys already know I belong to the "no bug too small" camp. And in a wiki environment, I'm more likely to make technical edits (spelling/grammar fixes, minor wording or structural tweaks, etc.) than anything else. That's apparently just how I roll.
I don't mind any bug being reported here, it's what this place is for after all. But I'd like to point out that another option for reporting bugs is to send me a mail, if you'd think it's too small for a new thread. I'm using a private bug tracker to keep track of bugs.
I don't mind any bug being reported here, it's what this place is for after all. But I'd like to point out that another option for reporting bugs is to send me a mail, if you'd think it's too small for a new thread. I'm using a private bug tracker to keep track of bugs.
Ah, the forum does have a PM feature available. I'll keep that in mind.
.png)
