Opened 10 years ago
Closed 9 years ago
#11856 closed enhancement (fixed)
Implement BMediaRoster::SyncToNode
Reported by: | Barrett | Owned by: | Barrett |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Kits/Media Kit | Version: | R1/Development |
Keywords: | SyncToNode | Cc: | |
Blocked By: | Blocking: | ||
Platform: | All |
Description
SyncToNode allow to set a performance time and get the function returns when the specified node reach this time. While i don't know one app that use this part of the BeOS API it should be implemented as it's a useful functionality and may become handy in future. It's anyway a missing part of BeOS API.
Attachments (3)
Change History (13)
comment:1 by , 10 years ago
patch: | 0 → 1 |
---|
comment:2 by , 10 years ago
comment:3 by , 10 years ago
I was a bit uncertain on how to handle those situations, i've fixed it in the new patch.
by , 10 years ago
Attachment: | 0002-Implement-BMediaRoster-SyncToNode.2.patch added |
---|
by , 10 years ago
Attachment: | 0001-Add-SyncToNode-test-to-NodeTest-and-update-it-to-act.patch added |
---|
Fix NodeTest and add SyncToNode test.
comment:5 by , 10 years ago
I'm trying to make my branch more slim so that i don't have too many beef on the roaster. I don't know what to do with the notifyPoint argument except use it for some logging.
comment:6 by , 10 years ago
The if statement in TimerExpired() is multilines, thus requires braces. The call to read_port_etc() has 0 as second argument, it should be NULL.
by , 10 years ago
Attachment: | 0002-Implement-BMediaRoster-SyncToNode.patch added |
---|
An attempt to be more consistent.
comment:7 by , 10 years ago
Is there something missing to get the code applied?
On a side note the MixALot sample code from Be is using this function.
comment:9 by , 9 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Some comments on the patch:
Is it correct to only check wait_port against these error codes ? Shouldn't this line read
Same thing later, in
You only check for B_TIMEOUT, although you check the "code" varibale later, but maybe you should also check if read_port succeeded ?