Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple issues with mx:Tree ( during dynamic updates with XML) #1198

Open
greg-dove opened this issue May 25, 2022 · 4 comments
Open

Multiple issues with mx:Tree ( during dynamic updates with XML) #1198

greg-dove opened this issue May 25, 2022 · 4 comments
Assignees

Comments

@greg-dove
Copy link
Contributor

Attached is both a Flex reference example (which works) and the current royale emulation of the same, which demonstrates the issues.

Also see the commit discussion thread at: acab343

(It is currently possible to enter an infinite loop when opening nodes using the royale example)

Additional Info
I will continue to work on unit tests for XML.notification, I believe I was seeing a case in swf where instead of "nodeAdded" here (

if (len > 0) xml$_notify("nodeAdded", this, firstChild, null);
) it was sending "nodeChanged" instead. I do have a local unit test for this, but I will improve the accuracy of the unit testing as well, because the trackChanges stringification in the current version is less than adequate.

(separate folders in the zip file for flex and royale - each contains a single mxml Application file)
mxTree_Issue.zip

greg-dove referenced this issue May 25, 2022
…th xml watchers. This can happen if changes are made in watcher functions.
greg-dove added a commit that referenced this issue May 26, 2022
@greg-dove greg-dove self-assigned this Jun 13, 2022
@greg-dove
Copy link
Contributor Author

I have 'resolved' this issue locally and will work over the coming weekend to a) explain the issues and b) create a branch for others to test with if there is sufficient interest in doing that before merging. As part of the work on this, I figured out why there are certain cases of infinite loops in XML notifications, for example, and I will explain that.

@greg-dove
Copy link
Contributor Author

@estanglerbm in particular I would welcome your input on this if you are available/inclined to do so, as you pretty much kicked things off here... and I am not sure why you weren't seeing some of the issues I was seeing, because I assume you are using dynamic Tree stuff somewhere in your code. Hopefully you might have a chance to try the changes against whatever codebase you are working on and provide additional feedback.

@greg-dove
Copy link
Contributor Author

Sorry, I will need a few more days before I can follow through on this. I suspect it will be the next weekend now.

@estanglerbm
Copy link
Contributor

I'll try to provide input. I just noticed updates on this issue (not getting email about it for whatever reason).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants