ok, nice, so you are just putting the browser into responsive mode (or whatever its called)

anything special in your project.xml?

allow-high-dpi

is true for HTML5 export, libraries:

xml
<haxelib name="flixel" />
<!-- <haxelib name="deepnightLibs" /> -->
<haxelib name="jsoni18n" />
<!-- <haxelib name="ldtk-haxe-api" /> -->
<!-- <haxelib name="hxcpp-debug-server" if="debug" /> -->
<haxelib name="haxeui-core" />
<haxelib name="haxeui-flixel" />
<!-- <haxelib name="hxbit" /> -->
<!--In case you want to use the addons package-->
<haxelib name="flixel-addons" />

haxedefs:

xml
<!--Optimise inputs, be careful you will get null errors if you don't use conditionals in your game-->
<haxedef name="FLX_NO_MOUSE" if="mobile" />
<haxedef name="FLX_NO_KEYBOARD" if="mobile" />
<haxedef name="FLX_NO_TOUCH" if="desktop" />
<!-- <haxedef name="FLX_NO_GAMEPAD" if="mobile"/> -->
<!-- Stop HaxeUI complaining about SSL since we don't use internet anyway -->
<haxedef name="haxeui_no_network" />
<haxedef name="no_macro_cache"/>

other than that, standard

cool - ill have a play

no_macro_cache

wassat?

when I first starting using haxeUI it would error out every time on hashlink, occasionally on windows, after the first build, unless I put that haxedef in there

this was 1.3.0 I think

fair enough, never seen that define before

think I got it from either gamma11 or maybe seifer? not sure

but it seemed to work

(didn't realise in that video, when I disable the touch emulation mouse cursor in video is hidden - screen capture program is bad at high DPI so it shows up offscreen instead)

and haxeui-core and haxeui-flixel are both git version btw

cool - well, the video is useful in the sense that i can see you are just testing a normal haxeui-flixel app in the browser with the mobile / responsive mode

so i can just try that and see what happens

this should be fixed now - if you we using it on an actual mobile device it would have been fine fyi, since there are certain

#if mobile

bits that changes the behaviour you were seeing - that said, i think testing on desktop using the mobile thingy is a valid strategy so the

#if mobile

type stuff has changed to a

if Platform.instance.isMobile

which allows for better detection (but also uses

#if mobile

if its there)

(git haxeui-core / haxeui-flixel)

Seems fixed now, thank you! https://plzlookat.mystupid.pictures/firefox_C8cqjggKl0.mp4

only reason I was using HTML5 with touch instead of native mobile is that I'm too cheap to buy a mac and dev license from apple just to use my own apps

heh heh, fair enough, either way, its still a valid testing strategy

and therefore it would be better for flixel (and haxeui-flixel) to act like a mobile when you are in an emulated mobile browser

arguably you could / should have just defined "mobile" for your desktop project, but no idea if that would break other flixel things - and i like the ability to check at runtime anyway

that was probably a more sane idea, but I'm also one of the rare people with a laptop with touch that actually uses the touch occasionally

pen/touch input feels much more natural for drawing-style operations like this drawing-tiles editor, imo

if it supported pen I'd have never needed to buy an ipad, but that gets locked behind expensive laptops even though the smarts are in the pen 😦

ok thank you for subscribing to my blog, cheers again

yeah, fair enough - tbh, i think the addition of

Plaform.instance.isMobile

is useful anyways, i mean its the platform its running on, not the platform its build for

it also fits in just fine with

Platform.instance.isWindows

/

isLinux

/

isMac

Is it possible to have structure and style in separated files (like a .html and .css) ?

sure