In a nutshell, Automatic Task Killers work by polling the OS for a list of currently running processes and the memory they are consuming. Then either with an intelligent algorithm or with user input the Task Killers issue a call to the system telling the system to kill the process. There are two apis you … Read more
Here is what you may want to do: public async Task<PewPew> SomeMethod(Foo foo) { // get the stuff on another thread var cTask = Task.Run(() => GetAllTheCats(foo)); var fTask = Task.Run(() => GetAllTheFood(foo)); var cats = await cTask; var food = await fTask; return new PewPew { Cats = cats, Food = food }; } … Read more
In versions honeycomb and up, you can use MoveTaskToFront like so //Bring Task to front with Android >= Honeycomb if (Build.VERSION.SDK_INT >= 11) { ActivityManager am = (ActivityManager) getSystemService(Activity.ACTIVITY_SERVICE); List<RunningTaskInfo> rt = am.getRunningTasks(Integer.MAX_VALUE); for (int i = 0; i < rt.size(); i++) { // bring to front if (rt.get(i).baseActivity.toShortString().indexOf(“yourproject”) > -1) { am.moveTaskToFront(rt.get(i).id, ActivityManager.MOVE_TASK_WITH_HOME); } … Read more
The answer is here http://blogs.msdn.com/b/pfxteam/archive/2011/10/24/10229468.aspx In effect the issue is that with new Task, and that it can only take a Action, whilst you are trying to give a Func<Task>. Here are the first two lines again, but rewritten using the correct overloads. Task t = Task.Run(async () => { await Task.Delay(2000); }); and Task<Task> … Read more
Your approach seems fine, so you probably just made some tiny stupid mistake. It’s actually pretty easy to make a simple custom TaskScheduler. For your case: void Main() { var cts = new CancellationTokenSource(); var myTs = new SingleThreadTaskScheduler(cts.Token); myTs.Schedule(() => { Print(“Init start”); Thread.Sleep(1000); Print(“Init done”); }); myTs.Schedule(() => Print(“Work 1”)); myTs.Schedule(() => Print(“Work … Read more
Does such a method exist? No. Is there any overhead to using an async method solely for this purpose? Yes. But it’s the easiest solution. Note that a more generic approach is an extension method for Task such as Then. Stephen Toub explored this in a blog post and I’ve recently incorporated it into AsyncEx. … Read more
The objective of the Tasks namespace is to provide a pluggable architecture to make multi-tasking applications easier to write and more flexible. The implementation uses a TaskScheduler object to control the handling of tasks. This has virtual methods that you can override to create your own task handling. Methods include for instance protected virtual void … Read more
Figured it out, the task should look like: namespace :test do task :new_task => :environment do puts Parent.all.inspect end end Notice the => :environment dependency added to the task
Does this get anywhere near your requirements? The behaviour falls somewhere between ExecutionAndPublication and PublicationOnly. While the initializer is in-flight all calls to Value will be handed the same task (which is cached temporarily but could subsequently succeed or fail); if the initializer succeeds then that completed task is cached permanently; if the initializer fails … Read more
JavaFX has Event Dispatch Thread which it uses for UI events. All work with UI should happen on this thread. And non-UI calculations shouldn’t happen there to avoid lags in UI. See next code: public class Indicators extends Application { public static void main(String[] args) { launch(args); } @Override public void start(Stage stage) { Pane … Read more