View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0026111||Runner||Functions||Public||2017-04-01 14:36||2019-02-13 13:33|
|Reporter||Dan||Assigned To||Russell Kay|
|Priority||Medium||Severity||C - General||Reproducibility||100%|
|Platform||-||OS||Windows 10||OS Version||Pro x64|
|Target Version||Fixed in Version|
|Summary||0026111: Functions: ds_list_priority_max() returns the last item with the highest priority, not the first, differs from docs|
|Description||ds_list_priority_max() returns the last item with the highest priority, not the first. So if I have "3, 4, 3, 2, 4, 4, 1" that 4 at position 6 (the penultimate value) is the one which is returned, not the one at position 2. Which differs from what the manual page for this function says.|
Expected: That the function does what the manual says. I.e., I get the 4 at position 2, then the 4 at position 5, then the 4 at 6, then the 3 at 1, the 3 and 3...
|Steps To Reproduce||1. Run the attached sample.|
2. Right-click at three different locations.
3. Your guy will have already started moving to the first location, so ignore that.
4. Observe he now moves to location 3 next, not 2, despite them having the same priority.
5. Observe you can continue to right-click to place more locations and keep him from going to location 2.
|Tags||No tags attached.|
|1.4 Found In|
|2.x Runtime Found In||188.8.131.52|
|2.x Runtime Verified In|
IJonesPriorityTest.yyz (28,833 bytes)
||This is not a bug as all the items are given the same priority in the sample|
Mass-closing as per the Resolution of Won't Fix.
If the comment from the dev above says this report was resolved because there was no sample, but you still have this issue in a CURRENT version of GMS2, please do submit a Helpdesk ticket and give us a sample project and we will add a new bug report with the fresh info.