If I can get it to work

if you want a hand with it just let me know. I don't mind spending some time stripping a few things away from it.

Im trying to run it from the package with nwjs since the app is knownly broken

GMEdit is another one that i had checked out, i was looking at it to see how the editor was implemented. Neat design in that one.

Just thought of something.... i had changed some values in my app that dealt with glPerspective and glOrth views..... i had set one of the cameras view to something outside of what was possible, caused my app to crash just like yours after pressing that button...... Double check your array or try a different arrangement in that mapproperties.hx to see if that stops the crashing. I'm still learning about arrays and memory allocation for them.... so your understanding is probably alot better than mine of them.

In my original code I populate that array from listing all the files in a folder using System, for this example project I uploaded here I just created a simple array in code, I can't how it can be wrong

haxe
// Loading tmx file list
{
  var files:Array<String> = ["bla", "ble", "bli"];

  for (file in files)
  {
    tilemap.dataSource.add({
      value: file
    });
  }
}

How can this be wrong? And on the other hand it works well in cpp target so... definetely the problem is in hashlink impl

i was wrong

doing some testing on mine.... i think i almost have it figured out.

its not your arrays, but the updating of information that is causing some kind of .... i can't think of a term for it..... but, almost like some headon collision

like a single thread or lane of traffic, then all of a sudden a car merges into the lane and blocks the flow, causing the crash

its the only way i can visualise it at the moment.

im experiencing similar issues when trying to update while live loading in hashlink, but i don't have that problem in other platforms.... so you are right, its with how we are handling the flow of info in hashlink.

speaking of which, gives me an idea of what to try on yours real quick. brb

line 75 in playstate.hx....... that is where your app crashes..

Between Mapproperties.hx and playstate.hx...... the issue is tied to that if statement

double check your nulls up to that point.... make sure its not trying to do something with a value of zero

guifes did you try this on windows and mac or just mac?

if you did it on mac and it crashed... me on linux and it crashed...... ian on windows and it didn't.... well... windows does like to let problems build up and then crash instead of right of the bat when it comes to any kind of mem allocation issues unless thats changed over the years..... i'll break out the win10 lappie and try it there as well.

crashes on this......... _mapPropertiesDialog.showDialog();

@User - do you still get that crash on the property grid? @User - your custom label (or any component) should work now, also, can you retest the issue with the textfield on a tab? I couldnt reproduce exactly but i did find something that was odd, so hopefully fixed it @User - morning! 😉

howdy Ian, i was trying to help

yeah, thanks Shaun, much appreciated for sure - ive been snowed under recently with COVID data analysis so havent had a huge amount of time to go through things

i know thats a chore ..... alot of data to crunch

you are rapidly becoming a "man of many backends" 😉

lol

> @User - do you still get that crash on the property grid? > @User - your custom label (or any component) should work now, also, can you retest the issue with the textfield on a tab? I couldnt reproduce exactly but i did find something that was odd, so hopefully fixed it > @User - morning! 😉 @bright-gpu-74537 yes I am

can you possibly zip a minimal example, just to make sure were looking at the same thing, as i cant reproduce (you might have already zipped one, but i cant seem to find it)

actually, nvm, i think i found it

when you comment out _mapPropertiesDialog.showDialog(); no crash.... makes me think its something with that command.