Higher available clipboard size

[Azzurite]

So when you do GLFW.glfwSetClipboardString a new MemoryStack for that clipboard is created. That stack has the default size of 64 kB.

We want to be able to copy/paste larger content. Are there any problems to look out for when setting the org.lwjgl.system.stackSize higher?

Since this is a general setting affecting all MemoryStack, not necessarily only applying to glfwGet/SetClipboardString, I don't know if this doesn't cause any negative effects if I set this to 512/1024/whatever.

[octylFractal]

For glfwSetClipboardString I would suggest allocating a separate byte buffer instead, and calling that overload instead of the String overload. For example:

String forClipboard = "my very long string";
ByteBuffer buffer = MemoryUtil.memUTF8(forClipboard);
try {
  glfwSetClipboardString(window, buffer);
} finally {
  MemoryUtil.memFree(buffer);
}
// Note: I didn't test this code, there may be minor errors. The general idea should be sound.

Depending on how much you use it, it might be worth allocating a single buffer up-front and re-using it.

For glfwGetClipboardString, it doesn't use MemoryStack at all, it decodes the bytes directly into a char[] (or byte[] on Java 9+) which is fed into the String constructor. So you shouldn't see any limits from LWJGL with that.

[Azzurite]

That was the question basically, what effect it would have. Thanks!

[SomeTroglodyte]

Increasing the System property just before a copy and tuning it back down immediately afterwards wouldn't work I assume, it will get read and stored long before?

[SomeTroglodyte]

Oh - "per thread that access MemoryStack," - rough estimate what proportion of candidates do?

[octylFractal]

Increasing the System property just before a copy and tuning it back down immediately afterwards wouldn't work I assume, it will get read and stored long before?

No, it's set up on first use of a MemoryStack anywhere https://github.com/LWJGL/lwjgl3/blob/master/modules/lwjgl/core/src/main/java/org/lwjgl/system/MemoryStack.java#L28

Oh - "per thread that access MemoryStack," - rough estimate what proportion of candidates do?

I'm not sure what you mean by that, if you mean what methods do, I don't think that's very useful information, but it's probably pretty low. Most LWJGL methods leave it to the user to allocate anything, and only the convenience methods that take e.g. CharSequence or return values from methods that normally take out buffers will be using it.

[SomeTroglodyte]

not sure what you mean by that

Your answer fits nicely, thank you!