lifter | A generic query engine , inspired by Django ORM | Object-Relational Mapping library

Your javascript object contains capitalized properties, while in your PHP code you are expecting lowercased properties.

Edit your JS code to

.value should not be in the argument to document.getElementById(), it should be used on the result of this.

And you shouldn't call $() or use the # prefix in the argument to getElementById(), the argument should just be the ID by itself.

To swap your Code Sandbox from TypeScript to JavaScript you should just need to:

1. Remove all typescript specific syntax from your ".ts" and ".tsx" files (interfaces, typings, etc)
2. Change all the file extensions to their JavaScript equivalent i.e. ".ts" -> ".js" and ".tsx" -> ".jsx".
3. Update the "main" property of the "package.json" file to point to the renamed entry point. i.e. "src/index.jsx".

I created a quick CodeSandbox with this already done.

...or at least an explanation of why gpiozero when_pressed is not playing nice.

My workaround was to have a private __capture() function, which acts as a wrapper to Clock.schedule_once(self.capture). capture_btn.when_pressed would use this private wrapper callback to avoid calling the problematic code directly, and any other uses of capture() would use the public one as normal since that works fine when not interacting with gpiozero.

In the following code I would prefer for capture() and __capture() to have swapped names since that would fit better with the philosophy of private functions, but unfortunately that's throwing AttributeError: 'RootWidget' object has no attribute '__capture' when I try that and I don't know how to fix that (using _RootWidget__capture isn't helping). The lines commented with ## illustrate my preferred but nonfunctional way.

I figured it out so I'll share my solution. There were two issues with my code. First, I realized that kivy.uix.camera.Camera is derived from kivy.uix.image.Image, so I checked those docs and sure enough, they said:

By default, the image is centered and fits inside the widget bounding box. If you don’t want that, you can set allow_stretch to True and keep_ratio to False.

This explains the widget resizing (i.e. the "imaginary box") but not the actual video feed. The other issue I had was that I was trying to set all the properties under the CameraStream: of , when I actually needed to set them under the Camera: of since it is the Camera object I'm modifying, not the CameraStream FloatLayout that contains it.

Resolving both of these issues made it work how I desired. For completeness, here is my updated lifter.kv file (the main.py file was unchanged):

The __init__() of GPIOButton is being called twice. Once when your build() method is called and self.root = LifterGUI() is executed. This creates the GPIOButton that appears in your GUI via the kv rules. The __init__() method is called again when ok_btn = GPIOButton(btn_gpio_pin = ok_btn_pin) is executed in your LeftSidebar class. This second call creates an instance of GPIOButton that does not appear in your GUI, but it is the one that is referenced in the update() method.

Since you already have setup a reference to the GPIOButton in your kv, you can modify the LeftSidebar class to use that reference:

1. In kv file, id: 'GoalsBN' is defined as a string.
2. id: 'GoalsBN' is defined in HomeScreen but not defined in ScreenManager, WindowManager:.

1. In kv file, id: is not a string. Therefore, replace id: 'GoalsBN' with id: GoalsBN
2. In kv file, add id: homeScreen and in Python script, add ids.homeScreen to self.root.ids.GoalsBN.add_widget(progressbar)

First off, assembly language is specific to the assembler, the tool that reads it. Not the target (arm, x86, mips, etc).

Function names are basically labels which means addresses. There is no real notion of functions, variable type (unsigned int, float, boolean, etc), address vs data vs instructions outside high level languages. Assembly generally has no real notion of these concepts, because they don't exist at that level. When computing an offset in an struct in order to access some item the base address and offset are just numbers when the add happens they are not addresses nor offsets, and they are only an address for the brief moment that that instruction executes, the one clock cycle when the address is latched and sent through logic toward the bus, otherwise its just bits.

Now saying that some assembly languages has declarations that use words like FUNCTION or PROCEDURE but these are not necessarily like high level languages where you have clearly divided boundaries.

And then there is compiler generated code vs hand generated code and with hand generated there is no expectation of these notions of boundaries.