wxWidgets Discussion Forum

wxPdfDocument supports this encryption method only for generating documents, but not for importing documents.

This might change with a future release of wxPdfDocument, but it is still unclear if and when this will happen.

I am trying to add file, and i have the results. 21:47:34: wxPdfParser::SetupDecryptor: Unknown encryption type (4). 21:47:34: wxPdfParser::SetupDecryptor: Unsupported V value. 21:47:34: wxPdfParser::SetupDecryptor: Import of document not allowed due to missing permissions. 21:47:34: wxPdfDocument:...

I've tried to reduce the code and locate the error. In principle, that is the right approach, but you need to do it in a reasonable way. Otherwise this will get you nowhere. First of all, it is still not clear whether you are using the shared or static build of wxWidgets, and whether your compiler ...

For quite a while you are presenting artifical examples here in the forum, which exhibit memory leaks for you under certain circumstances. Without full information which steps exactly you take, it is extremely difficult to give you useful advice. As with any memory leaks you have to track down where...

I have just a small (and not very important) question : is there a reason for using other build targets names than the ones used for wxPdfDocument ? wxPdfDoc has targets names like debug/release_win32/64 wxSQLite3 has targets names like debug/release_x32/64 Well, to be frank, there is no specific r...

Hi Xav' I've done the tests. I've tried to build wxSQLite using the following configurations : MinGW-w64 Gcc-7.3.0 / MinGW-w64 Gcc-8.1.0 / Gcc-9.2.0-TDM / MSYS2 Gcc-10.2.0 32 and 64 bits Shared and Static Multi-libs and Monolithic Release and Debug Great. Thanks a lot for doing all this work! I also...

In the meantime I tested to build wxSQLite3 with MinGW myself, too. I tested the 64-bit and 32-bit build using prebuilt wxWidgets libraries (version 3.1.4). The MinGW compiler versions are reported as 64-bit: gcc (x86_64-posix-seh-rev0, Built by MinGW-W64 project) 8.1.0 32-bit: gcc (i686-posix-sjlj...

For my own tests of compiling the underlying encryption extension with MinGW specifying -march=native was enough to make it compile. However, I don't have much experience with MinGW, so please try additionally the following options -msse4.2 and -maes . With these options, the builds succeeds (MinGW...

In the meantime you can try to add the compile option -march=native to the defintion of the symbol ALL_CFLAGS (and maybe ALL_CXXFLAGS ) in the makefile for wxSQLite3. This should allow MinGW to compile wxSQLite3 successfully. Tested : I've added -march=native at the end of lines 64 and 65 of sqlite...

Hi Xav' I've tried to build this last release with MinGW (Version 8.1.0 - 32 bits from MinGW-w64), but I failed. I tried with the default options with the following command line : mingw32-make config=release_x32 wxsqlite3 Here are the output I obtain: "==== Building wxsqlite3 (release_x32) ====" sql...

Version 4.6.3 of wxSQLite3 has been released. It supports version 3.34.0 of SQLite . This version is compatible with wxWidgets 2.8.12, wxWidgets 3.0.x, and wxWidgets 3.1.x. What's new in this release Upgrade to SQLite3 Multiple Ciphers version 1.1.2 Upgrade to SQLite version 3.34.0 Added method wxSQ...

Very weird. Without finding out what's actually leaking, i think we won't make any progress. Did you try VLD? Tried VLD, one line said "No memory leaks detected", another said "Detected memory leaks" If you are using poppler and/or wxwidgets as DLLs, you probably included the VLD header file only i...

how to do as below? If you need to access the same database from different threads you should open a separate database connection for each thread, then you are safe. Simply use one wxSQLite3Database instance per thread. Call its Open method on thread initialization and its Close method on thread te...

cutecode wrote: ↑

Fri Dec 04, 2020 9:28 am

Greate thanks for your job.

You are welcome.

I applied a fix a few minutes ago. Now an assertion should no longer occur.

Thank you, now it is ok. Good news. But now I have an assertion ASSERT INFO: ../src/common/unichar.cpp(52): assert ""Assert failure"" failed in FromHi8bit(): invalid multibyte character BACKTRACE: [1] wxUniChar::FromHi8bit(char) [2] wxPdfEncrypt::CreateDocumentId() [3] wxPdfDocument::PutTrailer() [...