Descriptive Problem Summary:When doing edits to a map that found incorrect data when opening it there is a possible crash for DM. If the last item on the list of objects that return incorrect data is just enough to not force a scroll bar but enough that the last line is off center that you can't click on it, you will not be able to access it. If you do try to access it DM to lock up and stop responding and you must then close it losing any unsaved work.
Numbered Steps to Reproduce Problem:Have a map with just enough errors to fill the box but not enough to force the box to create a scroll bar.
Code Snippet (if applicable) to Reproduce Problem:
Expected Results:To be able to edit the last item on the list.
Actual Results:DM stops responding.
Does the problem occur:
Every time? Or how often?Everytime
In other games?N/A
In other user accounts?N/A
On other computers?Only one to test on.
When does the problem NOT occur?When the scroll bar is created or the box for the error fits perfectly in the window.
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)
I updated from 443 and had no issues with that and earlier versions.
Workarounds:To predict what tile is going to error and code to so DM doesnt see it as an error making the list too small to go off the window.
ID:85740
![]() Nov 15 2009, 6:14 pm
|
|||||||||||
Resolved
| |||||||||||
Yes this one is hard to explain for me. You need a map with work already done. Change your code so the code doesnt match the objects on the map causing the pending error window to appear when opening the map. When the list of objs that you can edit fills to the bottom of the pending error window, the window usually turns on a scroll bar to go down to see more of the list.
In this case the list doesnt make the bar appear but is too long to access fully. DM just freaks out when you try to click on an obj in the list to edit or delete that isnt fully in the window and it cant scroll into the window, it causes unwanted behavior resulting in DM not responding. |
Some kind of demo would probably help here. I'm still not grasping what you mean.
|
http://files.byondhome.com/Dpheonix7/sample.PNG
This is the window Im talking about. See how it has /turf/sample as a pending error. If there was another turf that was pending too it would be added after the /turf/sample. If this list becomes long enough to reach the bottom of this window usually a scroll bar is added so you can move further down the list. But if the last object in the list doesnt go down far enough to make a scroll bar appear but is still down far enough to not appear fully in view because of the windows bottom border then the bug happens. When you try to access the last object in this list DM can not bring it into proper view for editing because there is no scroll bar and results in the crash of DM. |
This bug report still needs a numbered list of steps to reproduce it, which you did not include.