After this latest update I'm getting a crash always on
Gui.update();

http://www.esenthel.com/community/showth...p?tid=2862
Can you rebuild your project in VS?
If it won't help please attach the callstack from crash.
Does the problem occurs in any sdk tutorials?

Build goes fine in all ways trough.. Also cleaned and did the regular routine.
If I remove the GUI.update() it works fine. Except I have no GUI

Atleast some tutorial with GUI.update() work fine so it must be something on my end.. The thing is it was fine before the latest update.

---

I have no idea why this could happen. I tried updating on a two seperate machines and both are giving the same result right after update.

Might be that there is something wrong in our code but it did work before the update so I really don't have any clue where to look from.

What is your code for Property management?

do you modify any property.button.user, property.text.user? or any user?

when you store the Properties in Memb<Property> props;
do you call any props.remove, or just add?

Quote:do you modify any property.button.user, property.text.user? or any user?

No. They are not touched anywhere.

Quote:when you store the Properties in Memb<Property> props;
do you call any props.remove, or just add?

I tried removing all the Memb and Memc stuff from the menu and there was only couple of them there anyway. Results did not change. Removing the Gui.update() Menu draws ok but does not update. I'm also having this same result anywhere else where I try to call Gui.update()

all Gui Objects are const_mem_addr (they need to be stored in constant memory address, does your codes comply with this requirement?)

the only thing I've modified in last sdk release was add Property::_changed private member pointer to function

and setup Property::button.func, Property::text.func, Property::combobox.func, Property::checkbox.func at the creation of the Properties

func was set to custom function with "&property" as the user parameter (address of the property)

so what you should look into is the possibility that the 'user' parameter gets somehow modified (points to invalid address), or the property object get moved somehow, and their address has changed, or you have some other bug.

Do you call 'remove' for Memb<Property> ? it could change memory address of some elements. I'll change Memb to Memx for props for next sdk release.

Is your property management codes long? (if it's not long, you could send them to me, and I could make a quick look)

Yeah they are pretty long and separated on several files.
I'll try to look into to it. I'm sure i will be able to pinpoint the exact area of error more accurately now that I know what the possibilities are.

Can you elaborate a bit. If I would want to create 20x progress bars. How would you do this?

Quote:all Gui Objects are const_mem_addr (they need to be stored in constant memory address, does your codes comply with this requirement?)

Has this been always the case?

I'm guessing that here is the problem mostly and it is going to need a lot of redoing..

yes it was always like that

you can do:

Progress p[20];
or
Memx<Progress> p; FREPA(20)p.New().create

you could use Mems, Memc too, but only if you'd allocate all memory up-front:
Mems<Progress> p; p.setNum(20); FREPAO(p).create
(but I don't recommend this, easy to make a mistake)

Memx is most recommended

Most of our stuff is done like Progress p[20];
If that is not the problem then I'm not really sure. But more and more it seems like its somehow related to these sort lines.

The new update did not fix the problem :(

Probably you have bug in your codes
EE editor works. I've tested.some tutorials. I've tested ineisis all work no problem

Yeah something has changed.. I can still get it work if I use 2 updated back.
Ill probably have re-write all the gui stuff.