'tradeOffers' event not fired reliably
See original GitHub issueCommit 2672916d7ea0a037068e6a45d1b729f96450a0ec is causing the tradeOffers
event to not fire if the user received a new trade offer after handling an old one, since the amount of incoming trade offers didn’t change.
- Is this intended behaviour?
- Should I update the
_lastTradeOfferCount
property manually after handling an incoming trade offer? - What was the reason behind implementing the check in the first place?
Thanks!
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Why isn't dispatchEvent firing? - Stack Overflow
First, the event that you are dispatching is not a bubbling Event . ... Then your event handler, since it is a child,...
Read more >bukson/steampy: A Steam trading library for python 3 - GitHub
steampy is a library for Python, inspired by node-steam-tradeoffers, node-steam and other libraries for Node.js. It was designed as a simple lightweight ...
Read more >Final Rule: Selective Disclosure and Insider Trading - SEC.gov
The requirement to make prompt disclosure is triggered when a senior official of the issuer learns that there has been a non-intentional disclosure...
Read more >Issue linkage and international cooperation - JSTOR
However, Hafner-Burton's study evaluates the impact of issue linkage on inducing certain behavior by a government within its state, not inducing cooperation.
Read more >The Puzzle of WTO Safeguards and Regional Trade ...
This reasoning is relevant when the injury determination is based on the totality of imports (in that event, even those imports not causing...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is fixed in v3.25.2.
Alright, thanks a lot for looking into it!