The latest releases of OpenTrack now support Tobii natively, I recommend going that route now instead of this method.
Thanks to user Henkeman in the comments, I
// Released under the MIT License | |
import * as React from 'react'; | |
export enum TransitionStates { | |
// `MOUNTED` means the child was mounted along with the parent transition group | |
MOUNTED, | |
// `ENTERED` means the child item was added AFTER the parent was mounted | |
ENTERED, | |
// `YEETED` implies the element has been removed, but we are still waiting |
function useDragProps(id: string) { | |
const [dragged, setDragged] = useState(false); | |
const [over, setOver] = useState(false); | |
const {startDrag, stopDrag, getDragged} = useContext(ChecklistManagerContext); | |
const onDragStart = useCallback( | |
(event: DragEvent<HTMLElement>) => { | |
startDrag(id); | |
event.dataTransfer.setData('text/plain', id); | |
event.dataTransfer.effectAllowed = 'move'; | |
setDragged(true); |
diff --git a/discord_app/modules/voice_panel/native/controls/VoicePanelControls.tsx b/discord_app/modules/voice_panel/native/controls/VoicePanelControls.tsx | |
index 47b462d2900..7430848a2b7 100644 | |
--- a/discord_app/modules/voice_panel/native/controls/VoicePanelControls.tsx | |
+++ b/discord_app/modules/voice_panel/native/controls/VoicePanelControls.tsx | |
@@ -279,7 +279,7 @@ function useControlsGesture( | |
...wrapperSpecs.value, | |
x: 0, | |
y: 0, | |
- width: windowDimensions.value.width, | |
+ width: getMaxDrawerWidth(windowDimensions.value.width), |
The latest releases of OpenTrack now support Tobii natively, I recommend going that route now instead of this method.
Thanks to user Henkeman in the comments, I
bool process_record_user(uint16_t keycode, keyrecord_t *record) { | |
if (timer_elapsed(tt_timer) > 500) { | |
press_count = 0; | |
} | |
switch (keycode) { | |
case TT_LL: { | |
if (record->event.pressed) { | |
if (layer_state_is(_LOWER)) { | |
layer_off(_LOWER); | |
press_count = 0; |
export function logChanges(newProps: any, prevProps: any) { | |
if (process.env.NODE_ENV === 'development') { | |
const changes = Object.create(null); | |
Object.keys(newProps).forEach((key) => { | |
const newValue: any = newProps[key]; | |
const oldValue: any = prevProps[key]; | |
if (newValue !== oldValue) { | |
changes[key] = [oldValue, newValue]; | |
} | |
}); |
{ | |
"id": "spikey-blobs", | |
"containerSize": 224, | |
"radius": 42, | |
"rings": [ | |
{ | |
"id": "51ec5877-e2d0-4a58-8076-2196ec53c880", | |
"strokeColor": "transparent", | |
"points": 50, | |
"spread": 14, |
So a couple days ago I reported a bug where one of the camera views was bugged, and it looked like this:
I actually don't know much about how to build third party planes in MSFS, but I saw that GotGravel had made some tweaks to the cameras and it looked as simple as just digging into cameras.cfg and making some tweaks, so I dug into a text
{ | |
"id": "1374:368", | |
"name": "Yellow - Warning messages - Idle statuses", | |
"type": "TEXT", | |
"blendMode": "PASS_THROUGH", | |
"absoluteBoundingBox": { | |
"x": 1460, | |
"y": 923, | |
"width": 240, | |
"height": 76 |
const memTester = (() => { | |
const api = { | |
_timer: null, | |
start() { | |
if (api._timer != null) { | |
api.end(); | |
} | |
let back = true; | |
api._timer = setInterval(() => { | |
if (back) { |