mistahmikey

I actually took a shot at "fixing" this issue, and was able to get past that particular one, but then ran into NUMEROUS other problems with errors due to problems...

I was able to fix this issue in a local branch I created from a clone of this repository. Unfortunately, I do not know how to create a pull request...

I do not know what to do with this information - is there something I must do to make this work?

> DoAction doesn't work? Try DoAction(1) When you use item:Salvage(), the Desynthesis control is not displayed - it directly desynths one item. What would be great is if you could...

I've dug a bit more into this, and the problem is occurring with single clicks on the last column in the table (created using the Columns widget.) For some reason,...

Here is about as simplified a "complete" snippet as I can provide. It is much simpler, but it accurately represents the structure of how the code is called: ``` GUI:Columns(5,...

Because it hard to find authoritative information about this stuff for all use cases, I just guessed that is how it was supposed to be used. So should that code...

FYI, I changed my code to essentially do the above, and now, none of the cells respond to the single mouse click. They do respond to double right clicks, however...

Another update - we updated to the latest (1.90.8), and the single click detection problem is still present for all columns for snippet version 2 above. Changing back to snippet...

Another observation - it looks like when using a selectable, you don't need both GUI:SetNextItemAllowOverlap() and SelectableFlags_AllowOverlap - using one or the other alone results in the same behavior.