History

audit use of QTimer intervals to make sure we're using Qt::PreciseTimer when appropriate

Brad Hefta-Gaub committed 9 years ago

Commit a72f6011 parent b56a15b15 files · +35 −21Browse files

Showing the changes to libraries/networking/src/ThreadedAssignment.cpp (1 of 15 files). Show all

Unified · Split

libraries/networking/src/ThreadedAssignment.cpp+2−2
@@ -27,11 +27,11 @@ ThreadedAssignment::ThreadedAssignment(ReceivedMessage& message) : · 26 unmodified lines
2727 _statsTimer(this)
2828 {
2929 static const int STATS_TIMEOUT_MS = 1000;
30− _statsTimer.setInterval(STATS_TIMEOUT_MS);
30+ _statsTimer.setInterval(STATS_TIMEOUT_MS); // 1s, Qt::CoarseTimer acceptable
3131 connect(&_statsTimer, &QTimer::timeout, this, &ThreadedAssignment::sendStatsPacket);
3232
3333 connect(&_domainServerTimer, &QTimer::timeout, this, &ThreadedAssignment::checkInWithDomainServerOrExit);
34− _domainServerTimer.setInterval(DOMAIN_SERVER_CHECK_IN_MSECS);
34+ _domainServerTimer.setInterval(DOMAIN_SERVER_CHECK_IN_MSECS); // 1s, Qt::CoarseTimer acceptable
3535
3636 // if the NL tells us we got a DS response, clear our member variable of queued check-ins
3737 auto nodeList = DependencyManager::get<NodeList>();

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t