* created tag Release_26_04
Feature requests, bug fixes, JSON/XML handling
* fix make_zip script
* updated CHANGELOG
Close log window when main app window is closed
Great idea, implemented in [r2017] .
* updated build scripts
* implemented FR#304: Close log window when main app window is closed
* bump release number
* updated wxSQLite3 to 4.12.2, SQLite3 Multiple Ciphers version 2.3.2 (SQLite version 3.51.3)
* update libCURL to v8.19.0_5 to address security fixes, also for ARM
Close log window when main app window is closed
* harmonise output folders and make bin folders for different processors architectures to appear at the same level
* show CPU architecture in about dialog
* update libCURL to v8.19.0_1 to address security fixes, also for ARM
* updated wxSQLite3 to 4.12.1, SQLite3 Multiple Ciphers version 2.3.1 (SQLite version 3.51.3)
* improve handling of special characters in UTF8 notation (like copyright symbol) for JSON and XML
* update libCURL to v8.18.0_4 also for ARM
* update libCURL to v8.18.0_4
Inability to check an updated item for differences (run a Compare) while the checking of all items is running
Closing for the reasons mentioned.
Allow Item list to scroll when manually rearranging Items
Closing due to missing feedback. Assuming fixed.
Adding headers to one item affects headers for other items
If what the AI believes is true, this bug should be fixed in [r2006].
* fix BR#294: Adding headers to one item affects headers for other items by applying the proposed changes
Hello Darkness My Old Friend...
The issues reported here that are related to dark mode and that are fixable have been addressed. Therefore, I am closing this one related to the changes commit [r2005].
I was able to fix that one. It was caused by an API that seems not to do what it is supposed to do... But I found a work.around.
The first issue you reported I am unable to fix as this need to be reported upstream to the wx devs. The second one: I see no API to change that colour the colours you an change are exposed already), so I cannot do anything here too. The third one: I don't see a thick line. Can you send a screenshot (any maybe open another ticket as this is not related to dark mode, please?).
* fix colour issues wrt dark mode reported in BR#302
Yes, I tried that. But there is 1 bug as well as 2 other areas that will benefit from improvement. I was able to isolate the bug. STR: Launch WCM Click the Tools menu Click the "Show log" menuitem Once the log opens, tap the Alt key once. Notice the colours in the log window change! Area for improvement #1: Allow the user to change the colour of slider bars. STR: Launch WCM Click the Tools menu Click the "Configuration" menuitem In the Configuration UI that opens, in the "Check" tab, notice there...
Yes!!!! Switching to Dark Mode and resetting all custom colors, worked like a charm :) Thanks! Maybe the attached could be improved, or I'm missing again something? Thank you Dimitrios
Yes! Switching to Dak Mode and resetting all custom colors, worked like a charm :) Thanks! Maybe the attached could be improved, or I'm missing again something? Thank you Dimitrios
Hello Darkness My Old Friend...
I guess you did not read the introduction note: If you switch to dark mode you have to reset custom colours once. The reason is that custom colours will always override default ones, but custom colours for the light theme are obviously not valid for dark themes. That should solve the issue, please report back...
WCM 26.02 Dark Mode Issues (?)
Same issue with the dark theme. Subscribing to this one.
I just noticed that #302 is an identical issue report. Sorry for the duplicate :( Please close this one.
WCM 26.02 Dark Mode Issues (?)
Thanks for looking into it. I'm super busy these days, so I only had time to run it through "AI" (yuck in its current state, but fast) to see if it could catch anything real quick. Here's what it said. Hopefully it won't be a wild goose chase, as "AI" is still so primitive and so often completely wrong. My apologies in advance if any time is wasted. In the CurlManager.cpp file of WebChangeMon, the error lies in how the struct curl_slist* chunk is handled across multiple requests. Specifically, the...
Hello Darkness My Old Friend...
* updated README for RPi
* created tag Release_26_02
- updated ReadMe files on SF.net
Feature requests, bug fixes, dark mode, HiDPI and WoA64
Feature requests, bug fixes, security and new compiler
* updated CHANGELOG
* adjusted release scripts
* code optimisations caused by updated wxWidgets UI code generator (wxSmith)
* allow settings the pixel size of icons in the list control to support larger icons on HiDPI screens (make sure you use at least 32x32 on these)
* updated wxSQLite3 to 4.11.2, SQLite3 Multiple Ciphers version 2.2.7 (SQLite version 3.51.2)
- updated copyright in PugyXML based on GIT
* bump release number
- eliminate obsolete project build targets
* remove (obsolete) non-optimisation build (O0)
- silence (LLVM) compiler warning
* added ARM(64) resource and manifest files
* prepared build files for WoA64
* added exchndl for WoA64
* added curl for WoA64
* update libCURL to v8.18.0_2
- remove O0 targets (optimisation off) as its likely obsolete now
* allow a few more colour customisations
Any news? Is that an accepted answer? Otherwise I would close the ticket.
Just as a feedback for now: I still don't know what to do with it. "Focus on item change" does what it is supposed to do. Also, when the check is running. I believe what is happening is tat at the time of your right-click you visually have selected the item, but the background check already focussed on the next one. Since the right-click is operated on the selected (=in that case also focussed) item you get the answer as expected, but not as intended by you. I would advise to either turn this option...
Just as a feedback for now: I still don't know what to do with it. "Focus on item change" does what it is supposed to do. Also, when the check is running. I believe what is happening is tat at the time of your right-click you visually have selected the item, but the background check already focussed on the next one. Since the right-click is operated on the selected (=in that case also focussed) item you get the answer as expected, but not as intended by you. I would advise to either turn this option...
OK, that is weird. Here: https://sourceforge.net/p/webchangemon/code/HEAD/tree/trunk/CurlManager.cpp#l1198 ...starting at line 1192 you can see how this is handled: Clean the list of entries Collect the (new) ones to be applied Apply the new list that contains only the new entries and no old ones Which means any old entries should be eliminated. What you describe would mean that this is not working properly. r I am using the API in a wrong way. Maybe I need a closer look... If you have an idea -...
Bug with tool command line tags and spaces
That's a good one - I did not think of. It is due to an old backward-compatibility piece of code. Before %old and %new was introduced, it used to be %1 and %2. I changed that for exactly that reason and actually deprecated %1 and %2 w/o removing these code portions. This is done now in [r1984].
* fix Bug#301 with tool command line tags and spaces by eliminating old compatibility %1 and %2 tag which is now entirely deprecated therefore
* make text boxes in config dialog appear properly for custom colours