subgrid | See the following for use cases | Machine Learning library

From the MDN article on cloneNode

Cloning a node copies all of its attributes and their values, including intrinsic (inline) listeners. It does not copy event listeners added using addEventListener() or those assigned to element properties (e.g., node.onclick = someFunction).

It seems like cloneNode might already be ignoring the event listeners you're trying to ignore.

If you're trying to clone a

Pthreads expect a callback function of the form void* func (void*), period. You cannot invent your own function format and expect it to work.

Furthermore the vr(x) etc parameters are function calls - you call the function once then use the result of that to tell pthread_create that it's a pointer to a callback function, which it isn't - it's just nonsense.

Also a function with a return type must always return something.

All of these problems could be avoided early on by configuring the compiler correctly, so that it gives errors upon encountering blatant bugs and invalid C, see What compiler options are recommended for beginners learning C? Correct use of functions is very fundamental stuff and something you need to grasp before moving on to more advanced topics like multi-threading.

Correct use, as was told in the friendly man:

When using a module nested inside another module, you need to ns() the id of the nested UI function. So here, mod_subGrid2_ui(ns("subGrid2_ui_1")).

Here is a minimal reprex:

I'll assume you are wrapping each "section" in some container element, like a div. This is important because we'll use the fact that the button and the div are in the same container to figure out which halfwaydowndiv goes with the button that was clicked:

Use PCF Builder for XrmToolBox and create the PCF Control with Dataset Template.

This will allow you to replace any sub grid with the PCF control and the data for the sub gird will be passed in the parameters in the context.

You also have access to the paging on the dataset.

You can do it like so:

If you're getting CORS error, and you are accessing your site locally (via filesystem, or Live Server) this error typically means that there is something wrong with your href path, src path, or with your file hierarchy. If you are using a node server, then this answer is probably not for you.

Filesystem and Live Server handle parent directories differently.

Live Server uses your opened folder (in VS Code) as the root, and does not let you go to parent directories above that.

Let's say that the folder that you open in VS Code contains only your index.html file, and your assets folder is in it's parent directory.

In this case, Live Server will not let you access the files in your assets folder.

Typically, ../ takes you to the parent directory, but in Live Server, if you are already set in the 'root' directory (the folder that is open in VS Code), then ../ will not take you anywhere.

This is different from your local filesystem, where ../ will take you up as many parent directories as you wish, until you reach the root drive.

What I suggest:

Keep your file hierarchy as simple as possible.

Have your index.html in the root folder for your project, and then keep your assets in subfolders, rather than parent directories.

• Project Folder

Contains index.html and your assets folder

• Assets Folder

Contains script.js and style.css

Then, in your html file, change your paths to assets/style.css and assets/script.js

This will allow your site to work for both Live Server and your local Filesystem. It will also make things easier when deploying your website online.

EDIT: Whatever folder you open in VS Code will be your root directory, and Live Server will let you access the files from there and all sub directories. If you are unable to move your assets to the project directory, then make sure you open the folder that contains your assets folder in VS Code. Then navigate to your html file and start the Live Server from there.

If you make a list with all your plots, you can use do.call to call grid.arrange on the whole list. It's easiest to make a list of plots if we write a little function to produce 1 plot. I changed your base_size to 10 to make the image fit better on Stack Overflow--you can of course change it back and customize the one_plot function however you'd like.

Your code uses the Xrm.Page object, which is deprecated on Dynamics 365 CE Online / Dataverse. You should use the new API; see Client API Reference - MS Docs.

Your function is called twice, because the onLoad function gets called twice by the system: first when the form is opened in "Create" mode, second when the data on the form is saved. After the data has been saved, the form page is not reloaded, but nevertheless the form's onLoad function is called again. This causes your script to attach a second onLoad handler.

Try this code. It is based on the modern script API. Make sure your form passes the form context to the onLoad function: