UI-Library | A library of all my UI elements | User Interface library

I have now found a solution myself. Will certainly not be the best, but it works and so serves its purpose:

It's a tricky problem!

Function pointers are simple to implement on the sender side, but they are difficult to use on the receiver side because they they don't have any context.

One issue is that a function pointer cannot point to a member function. That's why you often see (C-style) frameworks pass an arbitrary void *userData to their callbacks, so you can cast your this pointer and retrieve it in that way. This still needs you to write a static wrapper function to cast the pointer back and call the member function.

A more modern solution would be to use std::function. This can contain a regular function pointer, a member function pointer, but also a lambda or a functor.

However, when you add context like this (or in some other way), you quickly run into difficulties with lifetimes. When the receiving class is destroyed before the sender, what is supposed to happen? If you don't do anything, this situation will result in undefined behaviour. A solution is to track on the receiver side to which events the receiver is subscribed, and unbind them before the receiver is destroyed. And this needs to be done in both directions: when the sender is destroyed, it also needs to notify the receiver that it should forget about the sender, otherwise the receiver would later try to unbind an event that no longer exists.

And I haven't even begun to think about multithreading yet...

There are libraries that solve these problems in various ways, for example eventpp (just found through a web search, this is not an endorsement).

Another one to mention would be the Qt toolkit, which went so far as to write their own small signals and slots extension to the C++ language (implemented as a code generator and a pile of macros) to solve this problem in a very ergonomical way.

If this issue happens while you're linking the local version of your library in your main project to speed up the development. It might be related to "duplicate version of React".

https://reactjs.org/warnings/invalid-hook-call-warning.html

This problem can also come up when you use npm link or an equivalent. In that case, your bundler might “see” two Reacts — one in application folder and one in your library folder. Assuming myapp and mylib are sibling folders, one possible fix is to run npm link ../myapp/node_modules/react from mylib. This should make the library use the application’s React copy.

In short:

• run npm link in /your-app/node_modules/react. This should make the React's global link.
• run npm link react in /your-ui-library. This should make the library use the application’s React copy.

I solved this by just copying the fonts as part of build steps. Basically, fonts have their own pipeline. There may be better ways, but this works well enough.

There are conflict libraries.

You said in your question that you are using jackson-core-2.10.3.jar

And in your dependency list, I see jackson-core-2.10.3.jar

Two different versions causing the conflict. It could probably be transitive dependency. Exclude the one you don't need.

You can refer another similar forum topic

It turns out to be a simple solution for me, but admittedly hard to figure out. The problem actually had to do with a require statement to load images in the code of the private package.

The function below was in the private package:

In your library go to the dist/library folder and run npm pack This will create a .tgz file of your lib. Then in your package.json file install the library from this packaged .tgz file. Like:

Put jquery.js file before jquery-ui.js file. Sequence matters.

BuckleScript removes a prefixed underscore character from reserved words when compiling to JavaScript, so you can name the prop _as and it will work: