There's also 'partial' failures, like it only rendering part of the view (missing the tabs at the bottom, for example), or not rendering the demo while still updating the tree view

thanks for your response, I'm not so sure it might take a while to make a minimal project. I guess we can start here - what role should

Screen.instance.root

have, and does

s2d

fulfil that role? Is a

h2d.Object

enough? Second, what is the actual way of adding components? On the website, they use

app.addComponent(mainView);

, but I don't think that translates into

haxe

. I don't know if simply creating the component and adding it as a child to a

h2d.Object

is the way to go or if I missed something?

so, in haxeui-heaps components are h2d.Objects, so you should be able to use them just like normal heaps objects - that said, there may be some bugs or oversights, so if you do get issues there, defo let me know (preferably with a minimal test app) and hopefully we can clear them up. the "root" for haxeui-heaps, is basically where things will go if you call

Screen.instance.addComponent(...)

, this is usually s2d, but i dont see any reason it couldnt be anything. fyi,

Screen.instance.addComponent

is used for things like dialogs, the popups for dropdowns, etc... and of course you own UIs

what browser? Ive been clicking around on Brave and all seems fine - although, interestingly i do get a load of

WARNING: trying to remove a child that is not a child of this component

although looking at your stack trace above, im guessing its going to be related to the "removing child that isnt a blah blah"

Okay I've got a minimal example working.. so I'm not sure what I did differently

always a fun point to be at 😄

if you managed to break the test app send it over - hell, send it over any if you want, i can take a look... maybe it will break this end?

¯\_(ツ)_/¯

Is it safe to put

xml

files in the

res

folder rather than making an

assets

folder?

shouldnt make a difference, xml files are loaded at compile time anyway, so shouldnt matter where you put them

im assuming you mean xml files for ui via ComponentBuilder

yes 🙂 I wasn't sure since

heaps

does something special with the

res

folder and embeds those assets

but in the minimal heaps example they have

-D resourcesPath=assets

so they change the path from

res

to

assets

(I think thats what that does)

ah that doesn't seem to matter, I deleted that nothing happened

@bright-gpu-74537 I use Brave as well. I have tried turning protection off, too.

i think heaps it probably does embed anything is res, not 100% sure myself, but either way, it shouldnt make a difference as haxeui uses xml files at compile time to generate haxe code to build the UI

what if.. UI is rendered off-screen? Could that be an issue?

ill try and fix the warning haxeui generates, upload the new explorer and maybe you can test again

Sure thing 🙂

i mean... it shouldnt do, but... maybe? :/

oh, so actually it looks like that is already fixed locally... will upload now

ok, if ctrl+f5 the explorer you shouldnt get the warnings anymore

do you still get the errors?

I reproduced! Sending to you imminantly

So, the UI should be following the cube, however when you hover over it the program freezes. You have camera controls as well as the progress bar animating to show that things freeze

(theres a bit of code duplication my bad)

huh, it seems removing that code duplication actually fixes the issue..?

i can repro though... on js and hl

where is the code dup?