Error: t.cols[ind - 1] has no properties

[frantik]

I get this error in the javascript console if i use any address besides the external ip, which is annoying when the ip changes. it causes the auto update feature to be disabled.

Error: t.cols[ind - 1] has no properties

Source File: http://xxx:xxx/gui/script.js

Line: 1777

FF1.5.0.2

[frantik]

some other minor issues i've noticed

- seems the search box doesn't like the letters "o", "p" or "a".. when typed they aren't displayed

- when adding a torrent the file upload form control isn't cleared

- when the add torrent feature is displayed you can't access the bottom scrollbar

- no way (that i can see) to force a download

- it's be nice if torrents could be added by url, and especially awesome if it was an HTTP GET request. this makes it possible to convert torrent links into links that will add the torrent to utorrent

[DonGato]

1. Already known.

2. Maybe a feature request.

3. Not reported yet, good catch.

4. There is none AFAIK.

5. Already requested.

[dAbReAkA]

3. was reported somewhere..

[DonGato]

Oh, I must have missed it then.

[frantik]

- CPU usage increases greatly when there are many torrents listed. I've got 25 torrents in my list right now, 7 active, and my CPU usage jumps to 70%+. Increasing the update time helps but there is still significant usage imo.. maybe even more than utorrent itself would take up! I'm running a lower end 1Ghz win98 machne (epia based entertainment center pc ) so each cpu cycle is really needed

[DonGato]

Well, don't use this interface then as it will be resource hungry for sure. There was an alternative being done in plain HTML. That should be lighter for you. Browse this forum for more info.

[frantik]

thanks for the tip.. i'll definitely check out other webUIs, though it still seems like an excessive amount of resources are being taken up considering all it's doing is refreshing a table every few seconds.

[DonGato]

Well, the problem is the browser, not µTorrent as most (all) the work is made by the client code.

[ICleolion]

1. Already known, already fixed.

2. Already mentioned, Directrix is working on it.

3. Was reported on bug tracker (which by the way you should really be using )

4. More features (possibly including this one) will be added in future releases.

5. Work has begun on this feature, not sure if it is complete yet.

CPU issue = is being worked on, Directrix should have less cpu intensive code for the next release.

[frantik]

bug tracker (which by the way you should really be using )

Sorry... I wasn't really clear on where these things should be reported and if beta testers were supposed to create bug tracker accts, etc. is there a set of beta tester guidelines or something you could direct me towards?

[ICleolion]

Nope, just that u keep the webui to yourself, and that u post bug reports with as much information as possible on the mantis bug tracker (that way u can see if a bug has already been reported).