Skip to content

Instantly share code, notes, and snippets.

View vonovak's full-sized avatar
👋
Open to opportunities

Vojtech Novak vonovak

👋
Open to opportunities
View GitHub Profile
@vonovak
vonovak / gist:7dcef431731a5e175a84f1767ba6ccfe
Created November 15, 2022 22:34
document-picker android build issue
info Starting JS server...
info Detected architectures arm64-v8a
info Installing the app...
> Task :react-native-gradle-plugin:compileKotlin UP-TO-DATE
> Task :react-native-gradle-plugin:compileJava NO-SOURCE
> Task :react-native-gradle-plugin:pluginDescriptors UP-TO-DATE
> Task :react-native-gradle-plugin:processResources UP-TO-DATE
> Task :react-native-gradle-plugin:classes UP-TO-DATE
> Task :react-native-gradle-plugin:inspectClassesForKotlinIC UP-TO-DATE
> Task :react-native-gradle-plugin:jar UP-TO-DATE
@vonovak
vonovak / RNTesterApp.android.js
Last active May 14, 2019 12:27
24734 test code
/**
* Copyright (c) Facebook, Inc. and its affiliates.
*
* This source code is licensed under the MIT license found in the
* LICENSE file in the root directory of this source tree.
*
* @format
* @flow
*/
@vonovak
vonovak / key behavior in react-navigation v1.x.x.md
Created April 29, 2018 19:33
key behavior in react-navigation v1.x.x

v1 behavior

In v1, key parameter is used as an identifier for the route to navigate to. If you provide the identifier (as for example in navigate({ routeName: 'someScreen', params: { someParam: 'someValue' }, key: 'someScreen' })) and user triggers such navigation action twice (eg. by pushing a button that calls the navigation action quickly twice in a row), the navigation action will be executed only once. The second call to navigate finds out that the route with the key is already present on the stack and instead of pushing a new instance of the same route, it calls setParams on the existing one.

Without using the key, calling navigate({ routeName: 'someScreen' }) twice would result in pushing the route onto the stack two times.

@vonovak
vonovak / FlowTypedMobxInject.js
Last active June 15, 2019 23:47
using flowtype with @Inject from 'mobx-react'
import type File from "File";
import type FileService from "FileService";
type FileDetailProps = {
file: File
};
class FileDetail extends React.Component<FileDetailProps> {
render() {
// remove the file prop and flow will complain!
#see http://ros.org/wiki/dwa_local_planner?distro=groovy for param description
DWAPlannerROS:
#default 2.5 -> with this value the robot sometimes gets to close to the wall when leaving a goal position in narrow corridors, causing dwa planner to have problems
acc_lim_x: 1.0
acc_lim_y: 0.0
#default 3.2
acc_lim_th: 2.0
@vonovak
vonovak / gist:b3cdf2c7f8d2df3952cd
Created May 4, 2015 11:21
new dwa params from the issue
#see http://ros.org/wiki/dwa_local_planner?distro=groovy for param description
DWAPlannerROS:
#default 2.5 -> with this value the robot sometimes gets to close to the wall when leaving a goal position in narrow corridors, causing dwa planner to have problems
acc_lim_x: 1.0
acc_lim_y: 0.0
#default 3.2
acc_lim_th: 2.0
@vonovak
vonovak / style.css
Created November 8, 2012 18:49
descr
/*
Theme Name: Flexible Child
Description: Child theme for the Flexible theme
Template: Flexible
*/
@import url("../Flexible/style.css");
h1.page_title {
font-size: 20px;