Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

uiOne SDK version 1.3.0.331641

<?xml version="1.0" encoding="UTF-8"?>

This TrigML may not be sensible, but it does compile, and when run causes a stack overflow. I would be happy to give you a full stack trace - or even debug this for you - if I had the Trigplayer source :)

It will work if you disable automatic variable observation -- otherwise it's pretty obvious why you end up with a stack overflow. The change in the text will trigger an observation callback, which will lead to a change in the text buffer, which will lead to an observation callback, etc. etc. etc.
That's not really something you can guard against at compile time -- granted, you could catch the obvious things at compile time, but the path to the buffer or the text could be a variable that's dynamically set.

It will work if you disable automatic variable observation -- otherwise it's pretty obvious why you end up with a stack overflow. The change in the text will trigger an observation callback, which will lead to a change in the text buffer, which will lead to an observation callback, etc. etc. etc.
That's not really something you can guard against at compile time -- granted, you could catch the obvious things at compile time, but the path to the buffer or the text could be a variable that's dynamically set.

mohlendo wrote:It will work if you disable automatic variable observation -- otherwise it's pretty obvious why you end up with a stack overflow. The change in the text will trigger an observation callback, which will lead to a change in the text buffer, which will lead to an observation callback, etc. etc. etc.
That's not really something you can guard against at compile time -- granted, you could catch the obvious things at compile time, but the path to the buffer or the text could be a variable that's dynamically set.
D'oh! Thanks Max....

mohlendo wrote:It will work if you disable automatic variable observation -- otherwise it's pretty obvious why you end up with a stack overflow. The change in the text will trigger an observation callback, which will lead to a change in the text buffer, which will lead to an observation callback, etc. etc. etc.
That's not really something you can guard against at compile time -- granted, you could catch the obvious things at compile time, but the path to the buffer or the text could be a variable that's dynamically set.
D'oh! Thanks Max....