Added mouse input handler and key input handle for JemiRecipe

[Sleepwalkerx]

I don't know for what reason it wasn't implemented, but due to the absence of this code, JEI recipes don't handle clicks and keystrokes.

[emilyploszaj]

It is a bit silly that it was never implemented. However, I don't really want to add and expose an API like this on DrawableWidget. It'd be fine to just create a new widget for JEMI input events that doesn't render anything.

[Sleepwalkerx]

Well, I made this code based on how you made DrawableWidget. I saw that you were creating a Consumer and decided to do it in the same style.
OK, then you propose to completely abandon DrawableWidget and make a separate widget for Jemi, or you want to create two widgets, but one for rendering and the other for intercepting inputs?

[Sleepwalkerx]

Just if I understand you correctly, you want to create two widgets on top of each other, only one will be with a render, and the other without.
I don't see the point in this when you can just move all the logic (including render and tooltips) to a new JemiWidget.

[emilyploszaj]

I was suggesting leaving the drawable widget as it is, and adding a new widget, even just an anonymous or internal class, that just handles the input events.

Thinking about it though, a new custom widget class (inside JemiRecipe) that handles rendering, tooltips, and input events for the JEMI display would probably be reasonable.

[Sleepwalkerx]

I did as you said. Check it out.

[SiverDX]

emi/xplat/src/main/java/dev/emi/emi/jemi/JemiRecipe.java

Lines 153 to 160 in 54b0490

	EmiDrawContext context = EmiDrawContext.wrap(draw);
	context.push();
	context.matrices().translate(x, y, 0);
	EmiDrawContext emiDrawContext = EmiDrawContext.wrap(context.raw());
	category.getBackground().draw(context.raw());
	category.draw(recipe, recipeLayoutDrawable.getRecipeSlotsView(), context.raw(), mouseX, mouseY);
	emiDrawContext.resetColor();
	context.pop();

why are you creating a second EmiDrawContext

[Sleepwalkerx]

emi/xplat/src/main/java/dev/emi/emi/jemi/JemiRecipe.java

Lines 153 to 160 in 54b0490

	EmiDrawContext context = EmiDrawContext.wrap(draw);
	context.push();
	context.matrices().translate(x, y, 0);
	EmiDrawContext emiDrawContext = EmiDrawContext.wrap(context.raw());
	category.getBackground().draw(context.raw());
	category.draw(recipe, recipeLayoutDrawable.getRecipeSlotsView(), context.raw(), mouseX, mouseY);
	emiDrawContext.resetColor();
	context.pop();

why are you creating a second EmiDrawContext

because it is done in the original logic. I don't want to break anything...

[Sleepwalkerx]

I removed it.

[emilyploszaj]

Other than the comment I have it looks good to me. Have you tested this with mods that use JEI's input features to make sure it works?

[emilyploszaj]

I'd prefer to use EmiScreenManager.lastMouseX and EmiScreenManager.lastMouseY just to reduce the use of calculations.

[Sleepwalkerx]

Other than the comment I have it looks good to me. Have you tested this with mods that use JEI's input features to make sure it works?

Initially, I discovered this problem when using the CustomMachinery mod and after these changes, the click in JEI began to work normally for CM. In general, I think it will work fine.