-
Notifications
You must be signed in to change notification settings - Fork 316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for SetCustomCursor in Krom #2872
Comments
Hi. I had the same question and @ MoritzBrueckner gave me a working solution, although it requires some manual source tweaking. RPaladin — Kha related, but people who use Kha claim that this code works fine in Kha but it doesn't for me in Armory - it also doesn't throw any errors for me so they may be well right. Why doesn't this code work in Armory it seems? timodriaan — Do you use Krom? The code looks correct to me, will try to reproduce it now (or do you already have a small example file)? RPaladin — timodriaan — Also doesn't work for me, will investigate. It definitely worked before (~ 1 1/2 years ago when I worked on my game jam game), but Armory's Krom.hx needed to be modified back then, perhaps it's a similar issue... timodriaan — It's only implemented in Armorcore, which is too bad because any change made to Kha would be overwritten when Lubos updates Kha. It's the same problem as always 😄 Discord message ID, if you're interested: https://discord.com/channels/486771218599510021/486773417316450305/1053045903293939722 @MoritzBrueckner in reference to asking Rob, were you able to get something implemented for Kha? |
I sadly don't remember this anymore (I don't even remember anymore whether I even asked), but there are essentially two issues here:
|
Krom dont supports change the cursor via kha.input.Mouse.setSystemCursor().
It was nice to have this possibility.
`package arm;
import kha.Image;
class MouseCursorHandler extends iron.Trait {
}
`
With this code above the mouse cursor is changed when exporting to Web, but in Krom this don't work.
The text was updated successfully, but these errors were encountered: