-
Updated
Apr 11, 2022 - TypeScript
state-machine
Here are 1,203 public repositories matching this topic...
-
Updated
Dec 1, 2021 - TypeScript
-
Updated
Apr 7, 2022 - Ruby
-
Updated
Mar 21, 2022 - Python
-
Updated
Apr 11, 2022 - OpenEdge ABL
I'm trying to replace the background diagram-maker canvas svg, with custom small circular nodes. So, probably this lead to more than 5000 number of circular nodes.
This is causing Performance Issues. Any suggestions, how to optimize this usecase?
-
Updated
Feb 16, 2022 - Python
-
Updated
Mar 9, 2022 - Java
-
Updated
Aug 14, 2020 - Ruby
-
Updated
Jan 23, 2019 - JavaScript
-
Updated
Apr 9, 2022 - C++
-
Updated
Apr 10, 2022 - TypeScript
If you think this will be the same for all apps you could just extract it into a separate .gradle file and apply to demo apps.
Something like:
./buildscript/configure-sample-app.gradle
apply plugin: 'com.android.application'
android {
defaultConfig {
testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
}
testOptions {
animationsDisabled = true
-
Updated
Oct 2, 2018 - JavaScript
-
Updated
Mar 15, 2022 - Ruby
-
Updated
Apr 7, 2022 - C++
Right now there is no easy way to expect that some particular worker is not running during the given render step. There is a workaround to use requireExplicitWorkerExpectations, but it requires to specify the footprint for the rest of the workers.
Proposal: add methods like expectNoWorker/expectNoWorkerOutputting that will do the work complementary to expectWorker/`expectWorkerOutputtin
-
Updated
Oct 21, 2021 - Python
-
Updated
Feb 6, 2022 - C#
-
Updated
Mar 5, 2022 - JavaScript
-
Updated
Mar 24, 2022 - Ruby
-
Updated
Feb 25, 2022 - TypeScript
-
Updated
Feb 6, 2022 - C++
-
Updated
Jul 12, 2017 - Java
-
Updated
Feb 5, 2022 - C
Also for iPad.
-
Updated
Nov 24, 2021 - JavaScript
Improve this page
Add a description, image, and links to the state-machine topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the state-machine topic, visit your repo's landing page and select "manage topics."