Surge 0.3.0 beta Random stuff I noticed

[no112358]

I'm not sure what's causing this difference in download. Might be something weird.
2.

I added a download and deleted it right after that and this warning showed.
3.


In "file transfers", if you arrange them by file AKA filename items on page one get arranged by filename and when you switch to page 2 they get arranged by name separately and so on. All the items should be arranged by name and then presented, not just items currently on the page.

If it were up to me I'd get rid of these pages and just have one place to show all items and then just scroll up or down to see them all.
4.

This laptops CPU is certainly not fast, but 10% usage seems a bit high, while Surge isn't really doing much, zero downloads/uploads. The number is 2-3% smaller if Surge is minimized. 21 items seeding.

[MutsiMutsi]

Thanks for the testing!

1. You've likely just deleted a file from surge, there will be chunks coming in up to a minute or so for chunks requests already sent, if the file is no longer present the bandwidth is only counted towards total client bandwidth in the bottom right.
2. That is expected behaviour; the error describes the consequence of your action here
3. We will look at sorting 👍

With regards to cpu usage, the current rendering engine seems quite inefficient, there is little we can do about that right now but it should be improved a lot with wails v2 and a chromium backend (currently IE11 engine). This also ties into our paging view; performance limitations from having a web frontend.

[MutsiMutsi]

update on 1 I now see what you mean, only 1 file is showing but all three files are actually pulling bandwidth at time of that screenshot, we will investigate.

[no112358]

It can't say a few seconds under remaining if the download hasn't even started yet. Certain downloads are stuck, low on seeds, but it still says a few seconds under remaining.

Now that Surge has dynamic size, the amount of items displayed should also be increased or decreased dynamically.

[MutsiMutsi]

Thanks for all these reports, I believe we have just finished every single one of these bugs reported. Coming in 0.3.1-beta.

[no112358]

Thanks for all these reports, I believe we have just finished every single one of these bugs reported. Coming in 0.3.1-beta.

Can't wait.