Hello, while going through library source code I’ve noticed that initialization logic in JM_new_lineart_device_Device includes functions to connect to mupdf, but doesn’t actually call them, which may result in seqno values being different.
At least based on what my intuition says it seems to be a bug, so I wanted to highlight that.
Is it supposed to be like that?
Welcome @sem0ark !
Yes, this is as it should be!
- For performance-critical features, there may exist two versions, a Python one (for debugging purposes) and one written in C++. A global parameter controls which one to use. Default is the C++ version.
You are pointing to the Python version.
- Device definitions consist of a list of callback functions, basically. Our code never calls the functions: there are called by our base library automatically whenever appropriate.
1 Like