640kb
640kb
``` 2023-10-11T10:22:58.9093231Z =================================== FAILURES =================================== 2023-10-11T10:22:58.9094249Z [31m[1m__________________________ test_ogcapi_records_pycsw ___________________________[0m 2023-10-11T10:22:58.9094776Z Traceback (most recent call last): 2023-10-11T10:22:58.9110680Z File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/_pytest/runner.py", line 341, in from_call 2023-10-11T10:22:58.9111818Z result: Optional[TResult] = func() 2023-10-11T10:22:58.9112802Z File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/_pytest/runner.py",...
I have updated the test. In the commit https://github.com/geopython/pycsw/commit/e1abe9bc9de68f5c25061be031269752a79d384e the number of entries for "conformance" and "queryables" have changed.
I have refactored the code and introduced the class SMimeMessage.
I also think that support for the XOAUTH2 authentication method would be useful. Is anyone already working on it?
I am also not an experienced MFC application developer (I only mentioned MFC as an example). But I have a small test application with which you can reproduce the problem....
> I tried your example but I'm such a Windows noob that while I got cmake-gui.ext to generate the project files and got VisualStudio to compile the source without errors,...
> @640kb I have created a windowProcedure branch with just added the Win32_Window::windowProcedure function pointer rather than the WindowTraits mechanism for doing this. If this works then I'd prefer it...
> And it mentions handling STRICT and non STRICT types differently. Do we need to declare Win32_Window.cpp windowProcedure using their suggestion? I'm also unsure about how to treat STRICT. This...
I am testing the new branch and will adapt my small example. If it works so far, I could submit it for vsgExamples.
I have added an example, see: https://github.com/vsg-dev/vsgExamples/pull/303