developer-tools

First of all, please note that everything in your program has a default location as per this. That's what applies unless you specifically tell it otherwise. For a function, that typically means that the function itself ends up in .text, a local variable inside the function in .stack and a string literal used by the function in .rodata. By allocating the function in a different section, that doesn't mean that those items inside the function somehow change location as well.

__attribute__((section... is similar to storage-class specifiers or type qualifiers (static, const etc) since it belongs with the object or function you place it next to. So you'll have to do:

I was having a play around with this today, and managed to get it working.

I installed an old (4.x) version of node as this is what the documentation said it worked with (I honestly didn't try anything newer as I couldn't get the simulator to do what I wanted so uninstalled it after).

The main issue was with node-ssdp, as the included package file with the simulator was trying to get it from a repo that no longer exists. After some trial and error, I found that if you edit the package file to specify node-ssdp 2.7.0 (which is the version that was released when the simulator was), the npm install should go through ok. (If you install a newer version the simulator crashes a few seconds after you run it).

Hopefully this helps!

The clue is in the compiler options you already posted:

-mfpu=fpv5-sp-d16 "sp" means single precision.

You told it not to generate hardware double instructions, which is correct for most Cortex-M7 processors because they can't execute them. If you have an M7 which can then you need to set the correct fpu argument.

By default, Next.js sets the X-Powered-By header to Next.js. So if you check Chrome's devtools for a page, you can check to see if this header exists.

Note: Developers can opt-out of including this header. So if the header does not exist, it is not evidence that the website does not use Next.js

Okey this problem is because useState is asyncronus. u can read more about this useState set method not reflecting change immediately.

I think the solution is add useEffect like this.

After a lot of researching and talking with folks everywhere, I managed to find the solution and I compiled it into a video. The video is in portuguese brazillian as it is my main language but if it helps someone, here's the solution:

https://www.youtube.com/watch?v=RRMPuZxi0fI

All the required files are in the video description but here's the steps that you wanna do:

1. Download the latest SDK 29 files from Android Studio SDK Manager or Embarcadero SDK Manager (In the video I show how to use Android Studio SDK Manager)
2. Replace some precompiled files in your Delphi installation folder, somethingsomething/Embarcadero/Studio/20.0/ Files in the video description.
3. Configure your SDK inside the Tools > Options > SDK Manager to the latest SDK 29 which is also shown step-by-step in the video.
4. Review your project configurations in Project > Options, make sure you have selected the Generate Android App Bundle option.
5. clean, build, deploy your .aab file, send it to the Play Store and you app now works for Android 10.

Now there is a fix available at quality.embarcadero.com!

Just one line has to be added to 'Androidapi.JNIBridge.pas'. I'm not sure if I should copy it here... Will update this answer when it is released.

The exception you're receiving is because this import has an error:

https://github.com/jimmckeeth/FireMonkey-Android-Voice/blob/master/JNIBridge/Androidapi.JNI.TTS.pas

..because JTextToSpeech_Engine has no JavaSignature attribute. It should be:

This is more of a comment than an answer, but…

Is your script changing the textarea value via direct DOM manipulation? e.g. document.querySelector('textarea').value = json? If so, it's likely that React doesn't see it because data/state generally flows downward into the DOM, not upward from the DOM.

My guess is that there's a React component that renders the textarea and registers a change listener on it. Change events from the textarea trigger a state update in the component, which rerenders the textarea to reflect the updated state.

You indicated that you've fired the change event, which seems like it should work given the scenario above. It's possible, though less likely, that the update is triggered via a keydown or keypress.

What I would suggest is that you install the React devtools in your browser and use the "Components" view to inspect the textarea component. It might give you some insights into the state of the component, what events it's listening for, etc., and it would let you see what (if anything) changes when you run your script.

It also includes a button that will open the source code for the selected component. (In minimized apps without sourcemaps it might be impenetrable, but it's worth a look.)