Code:
Problem description:
I have a problem with sometimes menus not being completely cleaned off the screen resulting in the player having to relog to fix the problem. Do to some issues I can't post the code but I will try to explain the current set up.
First all menus are created through datums. There is a menuobject list and the menu parts are objs added to the clients screen.
Now when a menu is cleaned out, it deletes all objs in the menuobject list then deletes the list to make a new one. Then calls client.screen.Cut(). Most of the time this works perfect, but if a little lag or something happens the menus only partially delete and parts stick on the screen.
ID:159969
 Dec 10 2008, 12:03 pm
|
|
I don't know how to check the client for it's lists.
There is no plan to reuse the lists later. The proc just makes new lists when called again. | |
Hmm? I don't quite follow what you're trying to say.
At any case, am I correct in understanding that you said, after calling client.screen.Cut(), sometimes (random?) screen objects remained? If you can confirm this, then it's a BYOND bug. | |
It's been confirmed about every 5 minutes on my game. I have also seen it on http://www.byond.com/games/TheFFAnotherWorldTeam/ AnotherWorld#online
| |
I have sent message to the coder of Final Fantasy 5 Another World. I have seen the same issue happen there and if they are using the same system to handle hud like I am, then we can get a clearer idea of what is happening.
| |
This is known as a 'screen bug' which has existed since screen objects were introduced. It's not possible to fix it, and the BYOND developers have never been able to track it down. You'll just have to live with it, sorry.
| |
Well that really sucks. It has defeated the use of a stat panel hud in battle. Something is very prominent in DW games. I myself can live with it, but it is killing my player base. If there was a way to make a verb or proc that could correct the issue it wouldn't be a problem.
| |
Hmm, maybe messing around with adding stuff to the screen and moving it around might work? I can't really tell though as I didn't experience this or made heavy use of screen objects.
| |
It adds and moves around just fine, its just when screen.Cut() is called sometimes parts of the objects randomly stay on the screen and act funny.
| |
Dpheonix7 wrote:
It adds and moves around just fine, its just when screen.Cut() is called sometimes parts of the objects randomly stay on the screen and act funny. What I mean is you could try moving stuff around the screen to try to clear the artifacts (screen objects remnants) once they're created. May not help at all, but it's worth a shot. A different method of clearing might also make a difference, though probably not. You could try screen = null, screen -= screen, for() loops... | |
Another thing you could try to clear the list is screen = null. This method works with multiple built-in lists fine, and with them you don't need to care about reinitializing the list later.