Activity for Morten MacFly
-
Morten MacFly committed [r70] on Code
* 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
-
You have to make sure that actually data that changes can be recorded. What type of check do you use? Header only and/or ping does only flag the item updated but there is no data that can be recorded. If unsure, please check the items' settings in the item's info dialog. I would wonder if there is really an issue with that, as this function is used quite a lot and you would be the first reporting...
-
The ability to enable/disable Items from the list of Items to check
-
Done the spelling correction in [r1966] BTW: Either the status bar or the tool-tip shows you the help for UI controls that are active. The message there would have hinted that you can select multiple items, too.
-
* spelling correction as suggested in FR#296: The ability to enable/disable Items from the list of Items to check
-
Adding headers to one item affects headers for other items
-
The reason for that is, that for a while now I record the received headers (esp. flags) and re-apply them on purpose. This helps in the case of user-IDs that are being computed and reduces the risk of being rejected due to any "clever" robot detection. Esp. in the case of sequential calls to the same page. I found this really useful and it does not hurt/break anything to my knowledge. Can you provide an example where this would screw the setup?
-
FR: Allow a RegEx-based "Post process" content keyword trigger
-
After all, I've implemented the request in [r1965] . It will be available in the next release (scheduled 25/12).
-
* implemented FR#291 Allow a RegEx-based "Post process" content keyword trigger
-
* fix bug in logic when to issue a post-process command (found in FR#291 FR: Allow a RegEx-based "Post process" content keyword trigger)
-
- fix spelling
-
* updated wxSQLite3 to 4.11.0, SQLite3 Multiple Ciphers version 2.2.5 (SQLite version 3.51.0)
-
- avoid warnings from style checkers (no functional change)
-
* switch compiler framework to work around linker issues with more recent cURL versions
-
* update libCURL to v8.17.0_2
-
* support folders with files as an alternative to ZIP archives
-
* build script: allow all builds w/o zero optimisation explicitly
-
* refresh ignore groups after item activated and add ignore dialogs
-
* make buttons more logically ordered
-
OK, I can guess what you have in mind ( and know sed btw. ;-) ) but I' afraid I need more info to be sure what to do. I guess it would be the best if you provide me with: 1.) A source JSON source file you want to process (which can be anonymized) 2.) The JQ command(s) you are operating on that file 3.) The expected output file Especially also flag why and where you want to add (?) line-feeds or similar. Wouldn't you usually want to remove these? I am using jsoncons ( https://github.com/danielaparker/jsoncons...
-
...?
-
* update libCURL to v8.16.0_9
-
* update libCURL to v8.16.0_6
-
* updated libJSONCons to v1.4.3
-
* updated exception handler (exchndl) to v0.9.8
-
* updated CHANGELOG
-
* created tag Release_25_10
-
* restored Linux target in project file that got broken
-
* fix linker error by using an old version of the PSL library of cURL on Windows (64 bit)
-
* bump release number
-
Feature requests, library updates, bug fixes.
-
- compiler update
-
* updated libJSONCons to v1.4.2
-
* updated crash handler DLL (exchndl) to v0.9.8
-
* update libCURL to v8.16.0_4
-
* updated libJSONCons to v1.4.2
-
* updated libJSONCons to v1.4.1
-
* updated crash handler (exchndl) to v0.9.13
-
- compilation fix wrt previous commit
-
...any news on that one?
-
FR: Add several additional "Post process" commands in Item settings
-
Implemented in [r1943] . But I did it slightly different. Its going to be a global setting in the tool registry. If you want, you can compile yourself from SVN to give it a shot. Otherwise the next release is planned for 10/2025, which is the regular schedule...
-
* implemented FR#292: Add several additional "Post process" commands in Item settings, slightly different
-
* fixed bug in logic with handling command on state change
-
- spelling fix
-
Likely to drop 32 bit support - feedback requested
-
BR: Environment variables in the Tool command
-
Fixed in [r1940] - thanks for reporting!
-
* fixed BR#293: Environment variables in the Tool command
-
- correct names of config sections
1 >
