Thread: 1.4.1 issues

I’ baaack…

*crickets*

Well, okay…I’m kinda back with a new account anyway. (Can someone fix that for me? It never sends me the reset email) Now that Bull has a build out I guess I need to track down James’ icon performance issues or revert the code. Reverting will be pretty ugly since the change was structural to ROL and Icons.

Do we have a list of things that need to be done before a release release?

There is still a blocking issue between Rismo’s code and ROL locks I think. I think it appears when you try to close WW in certain circumstances.

So I think I own the only two (or 1 and a half) show stopper bugs. The whole thread safety stuff within WW.Net needs a good looking through.

I have a mix of the old code and new code that draws my 5000 or so icons OK. I think the changes are pretty much limited to Icons.cs, world.cs, RenderableObjectslist.cs, and RenderableObjects.cs. I can zip up the old code and post it here if it helps. I can also try to make a static KML file that will display a good number of icons if that will be of help. Maybe I already did that. I wll have to check.
Thanks,
James

The issue with Rismo’s code is that he had pushed ROL deletes into a list that were then handled on the main (gui) thread. But you need to do this for both adds and deletes because you can end up with blocking for either one.

The problem then was things in WW and plugins assumed that an add or delete happened immediately so you’d end up with breakage because somethings avoided using the getters and setters but hit the ROL array directly. They would do an ROL.add(…) then try to get at those objects immediately and they weren’t there. Or they’d do an ROL.remove(…) and maybe do a dispose on it or something else not nice. So when you got around to handling deletes the object was bad or in some not good state.

The breakage can be pretty obvious (crash) or somewhat more subtle (ROs don’t render or behave right).

I don’t remember what is in the code right this minute but add and deletes need to be immediate OR we need to make sure everybody is going through the setters and getters for ROs.

The latter is the "right" way of doing things but requires the most work and most breakage among plugins. If you do the first way, we need to get rid of any calls to the gui thread that might block. The biggest thing that does this is probably his reporting of status to the download page from his worker threads.

Originally Posted by bull

More problems with the code –

<Nowak> ah btw. that 1.4.1 alpha has some problems handling "no tile there" tiles
<Nowak> basically it freezes the downloads of other tiles if you zoom into a region of "no tiles"
<Nowak> zoom out and zoom into a region with data
<Nowak>
<Nowak> ah, and if i return 404 when there is no tile
<Nowak> ww will just loop over requesting the same tile again and again and again
<Nowak> got a nice 2 screens worth of logs requesting same tile
<Nowak> before i changed getTile
<Nowak> http://rafb.net/p/kXCldj53.html
<Nowak> basically world wind saying "laalalalalala, i dont hear you!"

Nigel what do you suggest, a revert or do you wan’t to try fixing it?

Who me? I’m working on WWJ now.

I guess I can look at it after I fix the ROL issues. Fixing 404 issues should be somewhat obvious. Maybe. I’m guessing whatever is catching exceptions isn’t dealing with 404s.

We ran into this problem when hitting our tile server on our closed LAN. If I zoom to a level where we don’t have tiles, WW just hammers the server for the same tile, even though the server is correctly returning a 404. Finally, I just had the server return an empty .jpg with the name of the tile being requested. That seemed to work. I’d love to get WW fixed though.
Thanks,
James

Originally Posted by bull

Yup you, you seem to be the only mature WW dev we have left still interested in .Net, how come everyone is switching sides on me

Hey I’m trying to figure things out in .NET!

Edit: oh you said "mature"