# callback A callback function is a function passed as an argument to another function and invoked inside it to perform a routine or action. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Suspending functions or flows into callbacks DevFeed: [Suspending functions or flows into callbacks]() Original publisher: [Read original article]() Published: 2025-08-11T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [kotlin-coroutines](), [Kotlin](), [Coroutines](), [callback]() Tags: [callback](), [coroutines](), [guide](), [how-to](), [kotlin](), [kotlin-coroutines](), [workshop-learning-programming]() ### AI overview A practical guide to converting Kotlin suspending functions and flows into callback-based functions using Kotlin Coroutines. ### Source excerpt A guide on how to correctly convert suspending functions or flows into callback-based functions in Kotlin Coroutines. ## How to turn callback functions into suspend functions or Flow DevFeed: [How to turn callback functions into suspend functions or Flow]() Original publisher: [Read original article]() Published: 2025-07-14T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [kotlin-coroutines](), [callback](), [functions](), [Continuation](), [API]() Tags: [callback](), [cancellation](), [continuation](), [coroutines](), [exceptions](), [functions](), [guide](), [how-to](), [interoperability](), [kotlin](), [kotlin-coroutines](), [suspend](), [workshop-learning-programming]() ### AI overview A guide to adapting callback-based APIs for Kotlin Coroutines. It explains how to convert callbacks that return one value into suspending functions and how to adapt callbacks that emit multiple values into Flows, including handling cancellation and exceptions. ### Source excerpt A guide on how to correctly convert callback-based functions into suspending functions or Flows in Kotlin Coroutines. ## How to force update (& test) your Android app using Google's in-app update library DevFeed: [How to force update (& test) your Android app using Google's in-app update library]() Original publisher: [Read original article]() Author: Jake Lee Published: 2024-11-09T00:00:00Z Content type: tutorial Language: en Sources: [Jake Lee's Programming Blog]() Topics: [LineageOS](), [Kotlin](), [Library](), [Google](), [callback](), [Code](), [Users](), [Gradle]() Tags: [android](), [callback](), [code](), [dependencies](), [google](), [gradle](), [how-to](), [kotlin](), [library](), [version]() ### AI overview A Kotlin-focused tutorial on using Google's Android in-app updates library to implement mandatory immediate updates, including Gradle setup, update checks, dialog handling, callbacks, and app closure when the user cancels. ### Source excerpt Earlier this year, I needed to add the ability to force update users of an app. Whilst I've used custom solutions in the past, Google has a standardised "in-app updates" library that does all the essentials for you! ## Fixing the iterative damping interpolation in video games DevFeed: [Fixing the iterative damping interpolation in video games]() Original publisher: [Read original article]() Published: 2024-05-18T12:22:15Z Content type: article Language: en Sources: [The Last Static Blog RSS]() Topics: [Game Development](), [Godot](), [callback](), [function](), [Mathematics]() Tags: [callback](), [fps](), [game](), [game-development](), [games](), [math](), [physics](), [prog]() ### AI overview This article explains why repeatedly applying linear interpolation for damping can make game behavior depend on the refresh rate. Using Godot examples, it analyzes the iterative formula and motivates a frame-rate-independent solution. ### Source excerpt As I'm exploring the fantastic world of indie game development lately, I end up watching a large number of video tutorials on the subject. Even though the quality of the content is pretty variable, I'm very grateful to the creators for it. That being said, I couldn't help noticing this particular bit times and times again: a = lerp(a, B, delta * RATE) Behind this apparent banal call hides a terrible curse, forever perpetrated by innocent souls on the Internet. In this article we will study what it's trying to achieve, how it works, why it's wrong, and then we'll come up with a good solution to the initial problem. The usual warning: I don't have a mathematics or academic background, so the article is addressed at other neanderthals like myself, who managed to understand that pressing keys on a keyboard make pixels turn on and off. What is it? Let's start from the beginning. We're in a game engine main loop callback called at a regular interval (roughly), passing down the time difference from the last call. In Godot engine, it looks like this: func _physics_process(delta: float): ... If the game is configured to refresh at 60 FPS, we can expect this function to be called around 60 times per second with delta = 1/60 = 0.01666.... As a game developer, we want some smooth animations for all kind of transformations. For example, we may want the speed of the player to go down to zero as they release the moving key. We could do that linearly, but to make the stop less brutal and robotic we want to slow down the speed progressively. Linear (top) versus smooth/exponential (bottom) animation Virtually every tutorial will suggest updating some random variable with something like that: velocity = lerp(velocity, 0, delta * RATE) At 60 FPS, a decay RATE defined to 3.5, and an initial velocity of 100, the velocity will go down to 0 following this curve: Example curve of a decaying variable Note velocity is just a variable name example, it can be found in many other contexts If you ## Kotlin Coroutines use cases for Data/Adapters Layer DevFeed: [Kotlin Coroutines use cases for Data/Adapters Layer]() Original publisher: [Read original article]() Published: 2022-11-15T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [kotlin-coroutines](), [Coroutines](), [callback](), [Concurrency](), [Databases](), [SQLite](), [Android]() Tags: [blocking](), [callback](), [coroutines](), [databases](), [functions](), [kotlin](), [kotlin-coroutines](), [sqlite](), [workshop-learning-programming]() ### AI overview This tutorial explains common Kotlin Coroutines use cases in the Data/Adapters Layer, including repository and provider implementations, adapting callback-based APIs into suspending functions, and handling blocking calls with an appropriate dispatcher. ### Source excerpt How do we use Kotlin Coroutines in the Data/Adapters Layer, how do we use callback or blocking functions. ## OkLayoutInflater: Improving Android XML Layout Inflation with Parallel Coroutines DevFeed: [OkLayoutInflater: Improving Android XML Layout Inflation with Parallel Coroutines]() Original publisher: [Read original article]() Author: Anjal Saneen Published: 2022-10-26T01:27:02Z Content type: tutorial Language: en Sources: [OkCredit - Medium]() Topics: [Android](), [XML](), [Code](), [Parsing](), [implementation](), [IO](), [callback](), [interface]() Tags: [android](), [android-app-development](), [androiddev](), [anr](), [coroutine](), [engineering](), [file](), [io](), [main-thread](), [memory](), [mobile-app-development](), [parallelism](), [parsing](), [performance]() ### AI overview This tutorial explains how OkLayoutInflater addresses limitations in AndroidX AsyncLayoutInflater. It describes the existing implementation's sequential background inflation and presents a coroutine-based approach intended to use parallelism based on CPU cores, helping recycler view items load and scroll faster. ### Source excerpt The loading of large XML layouts is one of the major performance bottlenecks in android. Loading XML layout into memory through IO operations and parsing views through reflection can be expensive. This is especially true when the XML file is too large or when initializing the layout view takes a while. We know that when the main thread performs some time-consuming operations, it may cause the page to freeze, and even more, serious ANR may occur. Androidx AsyncLayoutInflater helps to load those layouts asynchronously. However, we found that it has some limitations. The goal of this blog post is to explain how OkLayoutInflater addresses these limitations. Source code analysis of AndroidX AsyncLayoutInflater https://android.googlesource.com/platform/frameworks/support/+/89f7eba/v4/java/android/support/v4/view/AsyncLayoutInflater.java Source code is short and easy to understand with only a few lines of code. In the inflate method, it creates an InflateRequest object and stores variables such as resid, parent, callback, etc. Then it calls enqueue to add the request to the InflateThread queue. The main purpose of InflateThread is to add requests to the blocking queue and perform BasicInflater.inflate operations in order. Regardless of inflating success or failure, the request message will be sent to the main thread for processing. The BasicInflater Inherited from LayoutInflater. In OnCreateView these prefixes are loaded on the layout. At last, mHandlerCallback implements handleMessage which executes the operation on main thread, and there is a fallback mechanism, that is when the child thread inflates fails. it will continue to inflate on the main thread, and finally, gives a callback to the main thread through the OnInflateFinishedListener interface. The limitations of AsyncLayoutInflater and how we improve it Single thread to do all the inflate work AsyncLayoutInflater has this major limitation. This was the main reason for creating a custom implementation. One of our r ## Kotlin Functional Interfaces: Function reference and SAM conversion DevFeed: [Kotlin Functional Interfaces: Function reference and SAM conversion]() Original publisher: [Read original article]() Published: 2020-10-17T00:00:00Z Content type: tutorial Language: en Sources: [Vasya Drobushkov]() Topics: [Kotlin](), [callback](), [interfaces](), [function](), [Java]() Tags: [bytecode](), [callback](), [class](), [code](), [function](), [function-reference](), [functional](), [interfaces](), [interop](), [introduction](), [java](), [kotlin]() ### AI overview This tutorial examines Kotlin functional interfaces, function references, and SAM conversion in a callback scenario. It explains that Kotlin 1.4 supports SAM conversion for functional interfaces, allowing callback objects to be created from function references. Although separate callback objects are created for different method calls, they delegate to the same function reference and the program behaves correctly; explicit callback instances can avoid repeated allocations. ### Source excerpt Introduction About two years ago I made a post about a tricky case in Kotlin-Java interop related to the usage of function references and SAM conversion. One of the points there was that in Kotlin, if interface is declared instead of a function, one has to explicitly create an object, therefore no caveats as with interop: val callback = object : ThirdParty.Callback { override fun onValueChanged(value: Int) { this@App.onValueChanged(value) } } With Kotlin 1.4 there is now a "Functional interface" which supports SAM conversion. And I've been asked on how it works in a similar situation. Let's find out. ## Decoding Handler and Looper in Android DevFeed: [Decoding Handler and Looper in Android]() Original publisher: [Read original article]() Published: 2019-12-24T00:00:00Z Content type: tutorial Language: en Sources: [Vasya Drobushkov]() Topics: [Android](), [class](), [callback](), [interface](), [Code]() Tags: [abstraction](), [android](), [callback](), [class](), [code](), [interface](), [object](), [parcelable](), [payload](), [thread]() ### AI overview This tutorial explains Android's Handler and Looper, describing Looper as an event-loop abstraction that drains a MessageQueue and Handler as an abstraction for posting, removing, and handling queued events. It also covers their relationships and the structure of Message objects. ### Source excerpt Introduction Handler and Looper are one of the main low-level Android OS things, which almost nobody uses directly (at least nowadays). But they are at the core, so many other high-level solutions are based on them. Therefore one should know what Handler and Looper are, what and how they are doing. In this article we'll try to understand Handler and Looper in Android. What, how and why we might need them. We'll start from some basic knowledge on classes and what they are doing, continue with relations between them. Then we'll look at each class separately trying to dive deep into details. And will finish with some canonical examples on where they can be used. ## Kotlin-Java interop: function references and SAM conversions DevFeed: [Kotlin-Java interop: function references and SAM conversions]() Original publisher: [Read original article]() Published: 2018-09-13T00:00:00Z Content type: tutorial Language: en Sources: [Vasya Drobushkov]() Topics: [Kotlin](), [Java](), [callback](), [interface]() Tags: [callback](), [function](), [interop](), [java](), [kotlin](), [lambda]() ### AI overview This technical article explains a Kotlin-Java interoperability issue involving Kotlin function references and Java single-abstract-method (SAM) conversions. When the same function reference is passed to Java registration and removal methods, the generated callback instances can differ, so the callback may not be removed as expected. ### Source excerpt Though all the things below are pretty obvious if being careful while dealing with Kotlin-Java interop, I decided still to write short note about one particular issue with function references (from Kotlin side) and SAM conversions (from Java side). Function reference Function reference is a good way to pass function as a parameter without explicitly using lambdas. For example, if we have function: fun method(callback: (Input) -> Output) { ... } then we can pass our function as a lambda with function call or as a function reference: ## Javascript's async/await and Promise in a few words DevFeed: [Javascript's async/await and Promise in a few words]() Original publisher: [Read original article]() Author: Graham King Published: 2018-07-27T14:30:45Z Content type: tutorial Language: en Sources: [Graham King]() Topics: [async/await](), [JavaScript](), [Promise](), [callback](), [Exception](), [Code]() Tags: [async](), [await](), [callback](), [exception](), [javascript](), [software]() ### AI overview This tutorial explains how JavaScript uses Promises and async/await to handle operations that could otherwise block its single thread. It shows how async/await makes callback-based asynchronous code appear more linear while failures are handled through exceptions. ### Source excerpt Unraveling the magic of async/await: From callbacks to linear code. ## ReactOS Menu and Submenu Interaction Implementation DevFeed: [ReactOS Menu and Submenu Interaction Implementation]() Original publisher: [Read original article]() Published: 2014-02-23T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [Toolbar](), [Windows](), [callback](), [Refactoring]() Tags: [callback](), [code](), [free](), [open-source](), [os](), [react](), [reactos](), [refactoring](), [toolbar](), [win32](), [winapi](), [windows]() ### AI overview A ReactOS development update describes implementing menu-item callbacks, submenu opening on hover, and related toolbar behavior. It also reports fixing an OnPaint return-value issue, comparing behavior with Windows, and refactoring menu code. ### Source excerpt The week began by implementing the functionality needed to handle clicking on menu items. This involved sending a callback notification for the currently selected item, asking the callback to execute the appropriate action of the item. Some of the items are not meant to be clicked on and are supposed to show a submenu instead. For these items I had to subclass the toolbar windows so that I could add a timer on hover and handle the opening of the submenu in the resulting WM_TIMER event, which would be received by the toolbar, but needed to be handled by my code. ## Asynchronous Control Flow with jQuery.Deferred DevFeed: [Asynchronous Control Flow with jQuery.Deferred]() Original publisher: [Read original article]() Author: Stephen Young (stephen.young@zumba.com) Published: 2014-01-16T00:00:00Z Content type: tutorial Language: en Sources: [Zumba]() Topics: [jQuery](), [callback]() Tags: [asynchronous](), [callback](), [how-to]() ### AI overview This tutorial explains how to adapt callback structures into callback queues using deferred objects, also known as promises, with jQuery.Deferred. ### Source excerpt How to adapt callback structures to callback queues using deferred objects (promises). ## JQuery and Django Autocomplete DevFeed: [JQuery and Django Autocomplete]() Original publisher: [Read original article]() Author: Map Published: 2011-02-26T03:55:56Z Content type: tutorial Language: en Sources: [Craig Kerstiens]() Topics: [Django](), [jQuery](), [web applications](), [JSON](), [callback]() Tags: [autocomplete](), [business](), [callback](), [django](), [filter](), [how-to](), [json](), [python]() ### AI overview A concise tutorial showing how to add lightweight autocomplete to a Django web application using a Django view, model filtering, JSON responses, callbacks, and jQuery autocomplete. ### Source excerpt In a couple of various places I've seen light requests of how to put autocomplete in for a Django web application. Here's a really light weight version with a view and autocomplete functionality using: from django.utils import simplejson def autocompleteModel(request): search_qs = ModelName.objects.filter(name__startswith=request.REQUEST['search']) results = [] for r in search_qs: results.append(r.name) resp = request.REQUEST['callback'] + '(' + simplejson.dumps(result) + ');' return HttpResponse(resp, content_type='application/json') For the jQuery autocomplete and call: ## Understanding this in JavaScript Objects, Inner Functions, and Callbacks DevFeed: [Understanding this in JavaScript Objects, Inner Functions, and Callbacks]() Original publisher: [Read original article]() Author: Graham King Published: 2009-02-23T02:06:41Z Content type: tutorial Language: en Sources: [Graham King]() Topics: [JavaScript](), [callback](), [bug]() Tags: [bug](), [callback](), [closure](), [javascript](), [local-variables](), [scope](), [software](), [window]() ### AI overview This tutorial explains how JavaScript's this behaves in object methods, inner functions, and callbacks. It shows how object context can be lost and how closures and local variables can preserve access to the intended object. ### Source excerpt "Navigate the tricky waters of 'this' in JavaScript objects and callbacks."