noe | patient management system for drive-through virology

Since you need to modify the menu list (NotesSelection) pass the value to that component and render it there.

NotesSelection component

You should mock function use, not function declaration.

There is an official implementation for that. You can add this dependency to your build.gradle:

the exam answer was that the function was returning a dangling reference

Correct.

but (...) does not present any undefined behaviour of the program.

What makes you think so? Undefined behaviour doesn't mean "program doesn't work correctly" or "program crashes". Undefined behaviour means exactly what it says: the behaviour is not defined by the standard. In fact it may work "correctly" (whatever that means), the standard doesn't prohibit it. That's why it is so dangerous. Because maybe in your test it works correctly, because of the hardware, OS, specific compiler, some other assumptions that take place. But the problem is that it is not guaranteed to work correctly. If you change machine, OS, a compiler (even switch optimization settings), a code slightly or even compile it two days later it may behave weirdly, in an (ekhm) undefined way.

In general there is no way to know whether a program behaves correctly or not, if UB is present. You are trying to analyze the situation by thinking about l-values, r-values, allocations, etc. while the reality is that when UB is present the entire program is meaningless. You just waste time.

Do not write UB code. Regardless of whether it seems that it works or not.

The glBegin()/glEnd() directives are used in compatibility profile of OpenGL as opposed to core profile which is more modern. However you are compiling your shaders in core profile using the line #version 330 core.

Even if the shaders are not compiled in the core profile, I don't think they'll work since I believe you can't pass vertex attributes with location indices (aPos, aColor) using glVertex3f.

I would recommend using the core Opengl for render calls. That means you should not use you glBegin()...glEnd() and pass vertex coordinates in every render cycle. Instead, the cube coordinates to GPU before-hand and let your shaders access those values:

1. Create VertexBuffer objects using glGenBuffers().
2. Store your vertex data in the buffer using glBufferData().
3. Extract the aPos and aColor attributes from the buffer and assign them indices of 0 and 1 respectively using glVertexAttribPointer().

This should work and no changes to your shader code would be necessary.

EDIT:

For rendering in compatibility profile, the data provided within glBegin/glEnd is ran through a default shader pipeline. You can't customize the pipeline using explicit shader code (like you did now), but you can modify some basic things in the pipeline (such as color, phong lighting, texture). So if you want to get the results your shader code represents, you need to do something like this:

After a long time I found the answer it is a bug in the new chrome, the solution is to build the app for Android 10, not 11.

I have modified your drawHelp function as follows:

add the row class in and add to the child div the col class according to the desired configuration, more information about Grid System, you can check inhttps://www.w3schools.com/bootstrap4/bootstrap_grid_basic.asp