GetHTML wxString progresscolor[] bug - #803
Conversation
|
Thanks @ZiTAL — the report is right, and the diagnosis is useful. That code sits in the One problem with the patch as it stands: it drops
Index 0 is genuinely dead code, but removing it shifts everything above it — and this compiles cleanly, so CI would go green while every progress bar rendered the wrong colour. Fix: keep all twelve entries and change only the type: static const wxString progresscolor[] = { wxS("transparent.gif"), wxS("black.gif"), ... };Minor: the new block is indented one tab deeper than the surrounding code, which clang-format will flag. One thing worth knowing before you put more work into this: amuleweb is deprecated. It still ships in 3.1.0, but it is slated for removal in a future release. The replacement is amuleapi, and it is not only a REST + SSE daemon — it bundles and serves its own web frontend (downloads, search, clients, categories, preferences, networks, with i18n), so it covers what amuleweb does rather than just exposing an API underneath it. If the web side of aMule interests you, that is where the effort will hold its value, and it is a far more pleasant thing to work on than the template engine. |
|
thank you @got3nks , I think now is OK, but you can edit by your own to fix my blunders... |
Element 0 was left as a bare narrow literal while the other eleven were converted, and a stray tab before the closing brace fails the clang-format gate. Both are cosmetic here -- wxString has a const char* constructor and the text is ASCII -- but a high-byte literal converted through the current locale can come out empty on a UTF-8 POSIX system, so the array is better off consistent.
|
Pushed two small fixes onto your branch (heads up: your PR head is your fork's Verified both ways with |
|
oh my god i'm fucking retarded |
|
No worries @ZiTAL, PR is merged now. 😂 |
Summary
Bug compiling the web server:
Test plan