There is a wide sweeping issue with all versions I have tested so far and the Remote Image server. I have yet to successfully 'send' background data to other clients when attempting to upload an image set on the background tab. This effects the Gilcrease versions, stable and development, and also Traipse.

Not one client has been able to 'send' the data to other clients. Instead they will see the image, but it will not be visible to others.

Basically this effects everyone. I don't know what is causing the issue but I am looking into it. Using the Remote Image Server for Miniatures seems to work ok.

Hm, if you like I can fix it tomorrow evening.

I am not sure what is causing the problem on my end. I get the path, it goes to the correct function, but the image stays on one side. Yeah, please fix it when you can.

This is for just the local image files? For internet image files there's a bug in 1.8.0+ dev that stops the file being loaded even by the first client. For 1.8.0 I seem to load the image file by url OK to the background but it doesn't appear on the other client(s).

I do recall we all messed up that code pretty badly about six months ago. Well I was going to move on to Grid features / testing / listing in the help wiki anyway. Except I had some odd bug in the Text View/ search dialog where it refuses to highlight the found text. Seems to have been there a while but something recent made things worse and now I can't get my text prediction stuff to work (not that i like or use it) and that ought to be a listed feature too. I suppose.

http://openrpgnotes.wiki-site.com/index.php/Chat

Hm. Well 1.8.0's issue with url image files (which also effected textures) was a simple merge bug. At least you don't have to worry about those cropping up in Traipse I suppose. I hate having to correct bugs twice because someone adds the old code back in.

Anyway that's as far as I got this morning.

Are you seeing this bug with LocalOrRemote set to "Local" or "Remote" ?
I can't even quite recall what the difference was....

Remote. The difference is Local is setup for CherryPy. Because people did not grasp CherryPy like I hoped for, I took your advice and switched the default to Remote starting {100505-00}

Oh btw did you see this?
http://s9.zetaboards.com/Mayhem_Gaming/topic/7203538/1/

The problem is in def on_browse(self, evt) in background_handler.py Possibly as a result of the split of Local and Remote the bottom 3 lines of the function are not called for Remote. Those 3 lines send the message. Now at first you think well just indent those 3 lines but the Remote part is handled with a thread so the image hasn't come back if you call those 3 lines immediately. I don't know if it used to not be threaded there. (Checked: it was always threaded and the 3 lines of code were never called so has it always been broken?)

One solution would be to add the calls to the thread code with an inline-y function. You could also try adding the calls to the end of the update function with a bit of fiddling. Either way i hope all the functions are thread safe.

Well here's my solution:

http://trac-hg.assembla.com/openrpg_dev ... ddb8a90610

oh. I see what the problem is. The three expressions

are only in the else: statement. Adding those after the if statement should fix it without writing a new function and thread.