View Issue Details

IDProjectCategoryView StatusLast Update
0026111RunnerFunctionsPublic2019-02-13 13:33
ReporterDanAssigned ToRussell Kay 
PriorityMediumSeverityC - GeneralReproducibility100%
Status ClosedResolutionWon't Fix 
Platform-OSWindows 10OS VersionPro x64
Product Version 
Target VersionFixed in Version 
Summary0026111: Functions: ds_list_priority_max() returns the last item with the highest priority, not the first, differs from docs
Descriptionds_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 Reproduce1. 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.

Repro: 100%
TagsNo tags attached.
1.4 Found In
2.x Runtime Found In2.0.5.49
2.x Runtime Verified In



2017-04-01 14:36


IJonesPriorityTest.yyz (28,833 bytes)

Russell Kay

2018-05-23 10:54

Manager   ~0059999

This is not a bug as all the items are given the same priority in the sample


2019-02-13 13:33

Adminstrator   ~0062925

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.