livings124 wrote:Debu: those controls have been like that since before 1.40 (on Tiger).
Thanks, but I assume you're referring to the priority controls in Torrent Inspector. I can live with that -- especially since I know where they are.
The start/pause buttons for individual torrents -- located to the right of each individual torrent status bar in the main Trans window -- didn't work in Beta 6 and do not work in the 1.5 final release. That is too hard to live with. That means that the only way to start/pause torrents is by using the "Pause all transfers" and "Resume all transfers" buttons at the top of the main Trans window. I almost always have completed torrents waiting to seed; I queue some of them up for seeding to a certain ratio and I hold some of them for possible future seeding - depending on perceived need. If I have to use the Pause all/Resume all buttons, I have to start all of them at once and must stop all of them, if any. Add to that the fact that the operation of the queue function is not exactly predictable, and the result is a loss of a whole lot of control over what is and isn't running.
Those buttons still work in Beta 5.
Anyway, I use those individual torrent start/stop buttons all the time (I almost never use the pause all and resume all buttons) and have a hard time seeing how I can reasonably proceed without them. I guess I could delete all non-running torrents and add them back in when I want to download/seed, or somehow work around the deficiency in other ways, but that seems terribly inconvenient.
I know you guys are working hard at stuff and it's your call as far as what is and is not functionally important, but from my perspective the individual start/pause button is a MAJOR feature/function. As such, it doesn't make a lot of sense to me to say that Trans 1.5 is supported under Tiger when those individual torrent controls don't work.
That's my take anyway. If you decide that that feature is not that important I'll just have to stay with Beta 5 until I upgrade to Leopard. (The reason I haven't is because DiskWarrior can't be run on my MacBook Pro except in firewire target disk mode from a computer running 10.4.11 -- last I checked anyway. I already have the Leopard system upgrade.)
In any event, thanks for the response -- at least I know I wasn't wasting my time posting my observations.