Hello, users of sol2! This issue was made so that I could get a better idea of what you all use for Lua and how much you like / dislike sol2 compared to what you used to use (if anything) and sol2 now. If anyone could just reply to this issue with their thoughts, perhaps answer some of the questions below (or go on a tangent, really anything), I'd appreciate it. I'm going to be writing a paper abo

Current documentation page for nana::label says:

Arrow cursor becomes a hand when the cursor moves over the red text. Meanwhile, it calls a web browser to open the URL by clicking the red text. NOTE: the url only works under Windows

with the NOTE part in bright red. I found this is not true as opening urls works just fine for

We have now MSVC 2017 support, but we should really make sure that it keeps working by adding CI, for example AppVeyor.

The very first example is https://github.com/cycfi/elements/blob/e50c5e70f92519a8e0b20a7b84c3e317d8a80ff3/examples/empty/main.cpp#L11 .

It's quite generic for almost all kinds of GUI applications that having a similar GUI specific app being created from client code. And of cause, app writers will have to do a similar app.run() invocation to bring up the GUI message loop or similar stuffs.

travis and AppVeyor need to be updated for OpenCV 3 and to work with the new eos version.
4dface builds just fine though, the build failures are just because travis and AppVeyor haven't been updated yet.

Doxygen has a @tparam command to document template parameters (https://www.stack.nl/~dimitri/doxygen/manual/commands.html#cmdtparam). We should probably use it in the library documentation.

Brief summary of issue / Description of requested feature:

More issues like #3458 solved

Steps to reproduce the issue / Reasons for adding feature:

• Texts have whitespaces at beginning or end to help facilitate layout

Error output / Expected result of feature

• Translators don't need to worry matching whitespaces around translated text.

Extra information, such as M

See thor's system/legacy-pc

In the array example program, we're copying data into arrays and from arrays. While we're checking the CUDA runtime API return values, we're not checking that the copying results in the expected data. We may be printing information from which it's possible to deduce that, but not actually checking.

Let's do that... @codecircuit ?

at the moment only ntw::system namespace and ntw::memory components are tested.
It would be great to have a test suite that covers most of the library.