StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19980308
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2013-11-14T14:31:10.930
FavoriteCount
0
LastActivityDate
2015-08-26T15:37:05.253
LastEditDate
2015-08-26T15:37:05.253
LastEditorUserId
2124387
OwnerUserId
2124387
ParentId
19768512
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
This is not a runLoop or ExternalAccessories problem. This is a daily OOP problem. The best way is to create a Communication object that can write to the outputStream and wait for response. Use @protocols to do this! (Event-Listener driven procedure) TRY THIS: First of all you have to attach input/output streams to a runLoop: <pre><code>[[session inputStream] scheduleInRunLoop:[NSRunLoop currentRunLoop] forMode:NSDefaultRunLoopMode]; [[session inputStream] open]; [[session outputStream] scheduleInRunLoop:[NSRunLoop currentRunLoop] forMode:NSDefaultRunLoopMode]; [[session outputStream] open]; </code></pre> Become their delegate: <pre><code>[[session outputStream] setDelegate:self]; [[session inputStream] setDelegate:self]; </code></pre> Once you become delegate you have to implement this method: <pre><code>-(void)stream:handleEvent:{}; </code></pre> This is the command to write out data to a stream: <pre><code>/* data is a NSData containing data to transmit. */ [[session outputStream] write:(uint8_t *)[data bytes] maxLength:[data length]]; </code></pre> This is an example code, (once you have session created, whereas the answer we expect is a byte): in Comm.h: <pre><code>/* Define your protocol */ @protocol CommDelegate <NSObject> -(void)byteReceived: (char) byte; @end @interface Comm <NSObject> { [...] id<CommDelegate> delegate; } @end @property (nonatomic, retain) id<CommDelegate> delegate; </code></pre> In Comm.m: <pre><code>@implementation Comm [...] -(id)init { [...] delegate = nil; [...] } -(void)write: (NSData *) data { [[session outputStream] write:(uint8_t *)[data bytes] maxLength:[data length]]; } -(void)stream:(NSStream *)stream handleEvent:(NSStreamEvent)_event { switch (_event) { case NSStreamEventHasBytesAvailable: /* This part will be executed every time your rx buffer contains at least 1 byte */ switch(state) { uint8_t ch; /* Read byte per byte */ [stream read:&ch maxLength:1]; /* now ch contains a byte from your MFI device ** and 'read' function decrease the length of the rx buffer by -1 */ /* Now you can notify this to the delegate */ if(self.delegate != nil) [delegate byteReceived: ch]; } break; } } </code></pre> your_app_controller.h: <pre><code>@interface MyApp : UIViewController <CommDelegate> { Comm comm; } @end </code></pre> your_app_controller.m: <pre><code>@implementation MyApp -(id)init { [...] comm = [[Comm alloc] init]; [comm setDelegate: self]; /* Now your thread is listening your communication. */ } -(void)write { byte out = 'X'; [comm write: [NSData dataWithBytes: &out length: 1]]; } -(void)bytereceived:(char)reply { if(reply == 'Y') { [self write]; //[self performSelectorInBackground:@selector(write) withObject:nil]; IT'S BETTER!!! } } @end </code></pre> Hope this helps!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBlocking communication with ios accessory
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTommaso Resti
UserOwnerUserId
1. USTommaso Resti
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POBlocking communication with ios accessory
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.