StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8347520
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2011-12-01T20:01:13.113
FavoriteCount
0
LastActivityDate
2011-12-01T20:01:13.113
LastEditDate
LastEditorUserId
0
OwnerUserId
795861
ParentId
8172235
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
It happens so because the lambda you pass to <code>Observable.Create</code> does not return the <code>CancellationDisposable</code> until it goes through all the steps. So, the order of actions is the following: <ol> <li>You call <code>Subscribe</code></li> <li>UI thread blocks</li> <li>On a <code>ThreadPool</code> thread, the execution enters the lambda</li> <li><code>CancellationDisposable</code> is created</li> <li>You check for cancellation several times and execute the whole process. During this, your progress bar is updated.</li> <li><code>cancel</code> is returned from lambda</li> <li>UI thread is released and <code>obs</code> gets its value</li> <li>You click <code>Button2</code> and call <code>obs.Dispose</code></li> <li><code>cancel</code> gets <code>cancel.Token.IsCancellationRequested=true</code>. But nothing happens since everything has already happened.</li> </ol> Here's the fixed code: <pre><code>private void button1_Click(object sender, EventArgs e) { var countObserver = Observable.Create<int>(observer => { var cancel = new CancellationDisposable(); // Here's the magic: schedule the job in background and return quickly var scheduledItem = Scheduler.ThreadPool.Schedule(() => { if (!cancel.Token.IsCancellationRequested) { //Step 1 of a long running process using lot of resources... observer.OnNext(1); } if (!cancel.Token.IsCancellationRequested) { //Step 2 of a long running process using lot of resources... observer.OnNext(1); } if (!cancel.Token.IsCancellationRequested) { //Step 3 of a long running process using lot of resources... observer.OnNext(1); } observer.OnCompleted(); }); return new CompositeDisposable(cancel, scheduledItem); }); obs = countObserver .ObserveOn(new ControlScheduler(this)) .Subscribe(i => { //Update a progress bar here... }); } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy this CancellationDisposable never get canceled on Observable.Dispose()?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USPavel Gatilov
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhy this CancellationDisposable never get canceled on Observable.Dispose()?
 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
 VTAcceptedByOriginator
2. 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.