Activity for Morten MacFly
-
Morten MacFly modified ticket #302
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 (?)
-
* 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
-
DARK MODE PLS
-
Implemented in SVN, [r13777] . Closing therefore. Note: Only available for wx3.3.x a above.
-
* implemented dark/light-mode for C::B as provided by wxWidgets version v3.3.x and above (closes FR#1567)
-
* 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
-
* welcome dark mode my old friend...
-
That is correct and it used to be my part of updating this control. However, the underlying scintilla did a huge change starting with a certain version (I don't recall at the moment) that I was unable to port to C::B. Maybe its worth another trial or, another option, accept that we loose some features of the (custom) control we use and switch to the "native" scintilla control that wxWidgets ships meanwhile (which wasn't the case for a long time another reason why there was/is a specific C:B control)....
-
That is correct and it used to be my part of updating this control. However, the underlying scintilla did a huge change starting with certain version that I was unable to port to C::B. Maybe its worth another trial or, another option, accept that we loose some features of the (custom) control we use and switch to the "native" scintilla control that wxWidgets ships meanwhile (which wasn't the case for a long time another reason why there was/is a specific C:B control). These are the options we ha...
-
We are on wx 33 already, see here for example: https://sourceforge.net/p/codeblocks/code/HEAD/tree/trunk/src/CodeBlocks_wx33.cbp I did not look into it so far, but if it is really easier with the wx33 support: Any patches are welcome!
-
* allow to fine-tune compiler output polling by exposing the respective polling timer values though compiler options
-
* updated libJSONCons to v1.5.0
-
* add a new compiler option to entirely silence all compiler output (temporarily) to improve compilation speed for large, (error-free) projects
-
* transition to the year 2026 (Happy new Year!)
-
* updated wxSQLite3 to 4.11.1, SQLite3 Multiple Ciphers version 2.2.6 (SQLite version 3.51.1)
-
* updated libJSONCons to v1.5.0
-
* updated translation files
-
* update libCURL to v8.18.0_1
-
* make use of wxIconBundle (later)
-
* added more icons in XPM format to make use of wxIconBundle (later)
-
* created tag 25.12
-
* updated changelog
-
* add support for special formats like Withings SmartWatches (values in CSV files represented as vectors)
-
* bump release version
-
* updated translation files
-
* created tag Release_25_12
-
- updated README for Linux after switching to Ubuntu 24.04-LTS and wxWidgets 3.1
-
* updated CHANGELOG
-
* compilation fixes for Linux distros using wxWidgets v3.x (and higher)
-
Feature requests, bug fixes, security and new compiler
-
Feature requests, bug fixes, security and new compiler
-
* bump release number
-
* update entire project to wxWidgets v3.3, libraries and flags
-
* update entire project to wxWidgets v3.3
-
* libPugiXML: inline static variable
-
- updated forgotten updated wxsqlite files (no functional change)
-
* updated build system to new compiler
-
* update to wxMathPlot library
-
* updated libJSONCons to v1.4.3
-
* updated libCVS to latest GIT HEAD
-
Crash when dragging an item below the last item in multi-column mode
-
This is fixed in SVN now [r937]. Thanks for reporting! Await the next release...
-
Ampersands in titles missing from notifications
-
Best way to help with fixing UI spelling/grammatical errors
-
"Set" button in Configuration -> Colours generates error
-
`Hide on minimise` option freezes system
-
The ability to enable/disable Items from the list of Items to check
-
"Find next..." behavior on the Add/modify item > Content page.
-
Implemented in SVN [r1968] . Closing.
-
* implement FR#299: "Find next..." behavior on the Add/modify item > Content page
-
This requires a full web browser (and likely also CSS and JavaScript) engine to work. By design, WCM does not make use of such. Instead, you can reduce / point to the sections by using all the features it provides instead, like Tags, Ignores, RegEx patterns and so on... I usually first strip down to what I want to monitor exactly by searching for the phrase in the content, then choosing the HTML (JSON...) items whatever comes just before that one and use it a start tag. Hope this helps. If not, please...
-
That's why XPath and JSONPath was added such that you can use what you' described above easily: /html/body/div[4]/div[1]/div[2]/table/tbody/tr/td/div/div[1]/table/tbody/tr/td
-
Allow Item list to scroll when manually rearranging Items
-
This is unfortunately a limitation of the underlying UI control that I cannot change. But you can use the keys "<" and ">" for that purpose. Additionally, in the "Items" menu you can sort alphabetically and if you introduce a certain prefix for the label of the items they become sorted as you wish. Let me know if that is of help for you and then I will close the ticket.
-
Inability to check an updated item for differences (run a Compare) while the checking of all items is running
-
You could also inspect the debug log once enabled under Options - Misc - (last section) Content Filter, Decision for Checks, Ignore pattern etc... and have all enabled in the log UI. Maybe then you'll find out yourself...
-
OK, for this to investigate I need an example webpage where this happens as it does not occur to me at all. Can you provide an example (webpage, steps to reproduce)? Thank you!
-
Alert box fatigue: "Regular expression is not applicable for the selected content (no matches found)."
-
Alert box fatigue: "Regular expression is not applicable for the selected content (no matches found)."
-
Implemented / improved in SVN [r1967] . Closing.
-
* fixed BR#295: Alert box fatigue: "Regular expression is not applicable for the selected content (no matches found)."
-
"Find next..." behavior on the Add/modify item > Content page.
-
Seems useful, indeed, but then should also work like that on other dialogs with a search function... I need to investigate how this can be solved properly though...
-
Don't scroll to the position of the item being checked when initiating the check of all items.
-
You can do this already under: Tools - Options - Misc - "Focus item on change" and "select item on change". I consider this BR invalid therefore. If you mean something different, please open another FR.
-
Alert box fatigue: "Regular expression is not applicable for the selected content (no matches found)."
-
Yeah, I never noticed the message appears several times. The reason is that the colouring is updated immediately so you can see if you grabbed the right phrase. I will think about a way how t handle this, e.g. one option would be to do this on the "lost focus" event, i.e. when you leave the textbox instead, while typing.
-
Inability to check an updated item for differences (run a Compare) while the checking of all items is running
1 >
