• Robert

    Nope. Also not sure anything but Windows still uses hardware cursors but maybe you can help me out getting up to date on the current state of affairs.

    posted in Kode read more
  • Robert

    Adobe sold Air, like, a week ago? Also I see no use for it with Kha, the flash/air runtime is way slower than all the other targets and the GPU features are from 20 years ago. It made sense as a fallback for Internet Explorer <= 8 (the JS runtime in IE9 already seriously outperformed flash) and for debugging back when Haxe only really supported debugging via flash - but that's it IMHO.
    The Node target also isn't updated regularly - also it's probably not what you think it is, it runs applications in headless mode for Kha's prototypical network multiplayer support.

    posted in Kode read more
  • Robert

    The Unity target is outdated since we have real console targets and I think about just throwing it away. Will have a look at that Flash error though (don't really care about that one anymore either though).
    With native IDE I mean Android Studio for Android, Visual Studio for Windows,... - the usual workflow is to develop using the html5 or Krom debugger in Kode Studio, then export to the "native IDE" for your target systems and run it in those to see what's going on if anything doesn't work.

    posted in Kode read more
  • Robert

    Nooo, that's not what I said. Kode Studio and the Kha extension pack have a khaPath option, there is no need to mess up the internal file structure which will then probably explode with the next update.
    For Android I think you have to put some stuff on the path but personally I always use the native IDE so that tends to work best. So what were the other targets you tried?

    posted in Kode read more
  • Robert

    It didn't find gradlew.bat. That's an Android thing, but for Android you'll have to upgrade Kha anyway, Android Studio changes too much and breaks old projects every other day. To do that, git clone --recursive the Kha github repository, then point Kode Studio to it via its khaPath option.
    What happens when you try to compile for Windows?

    posted in Kode read more
  • Robert

    Well, use vscode with the Kha extension pack then. Hopefully the error disappears with the next Kode Studio update, when I merge the latest vscode changes.

    posted in Kode read more
  • Robert

    Hey, no worries. Tell us when it doesn't work, I don't have a 32 bit installation to test on.

    posted in Kode read more
  • Robert

    The Kha extension pack includes everything you need. It's hard to use because it's so easy to use apparently 😄

    posted in Kode read more
  • Robert

    That weirdly aggressive thread title keeps me from explaining to you how to do the first option 😛

    posted in Kode read more
  • Robert

    Uh oh. I have no idea, haven't seen that before. Can you check whether regular vscode works on your system?

    posted in Kode read more

Looks like your connection to Kode Forum was lost, please wait while we try to reconnect.