glutin | level library for OpenGL context creation | Game Engine library

Since *ngFor is placed on the td tag it ends up creating multiple td tags, one for each element within element.Ingredienti and element.Allergeni. What you want is to display the whole element.Ingredienti array within a single td. So generating some other tag within a single td is the way to go.

Something like this should solve your issue

What you want is to destructure your structure to get its parts, so that you can move only one of them to the closure:

I solved this particular issue by making event_loop of type Option<()>> and the run method invoking self.event_loop.take().unwrap().run(...). Unfortunately I really dislike the semantics of this solution since in theory the event loop exists during the entire lifespan of the window and my solution leaving a None in its place doesn't feel right at all.

OpenGL is implemented as a library with a C ABI. If you want to call a C function from rust, it always means you have to use unsafe because the C implementation knows nothing about the safety features of rust and naturally doesn't support them. Furthermore, OpenGL uses raw pointers in its API to pass data from or to the GL, which also requires unsafe code in rust.

This is apparently a bug in an old version of winit, which is fixed in the latest winit release. However, various crates e.g. amethyst, piston, ggez, etc. still use winit 0.19. In Rust 1.48.0 the issue has apparently manifested itself as a panic.

On the amethyst issue tracker a comment mentions, that for now a possible workaround is to revert back to Rust 1.47.0. If you're using rustup, then you can do that by executing the following command:

According to the documentation for GetUniformLocation:

This function returns -1 if name​ does not correspond to an active uniform variable in program​, if name​ starts with the reserved prefix "gl_", or if name​ is associated with an atomic counter or a named uniform block.

So you're not error-checking your gl calls, and it looks like there are cases where you're calling GetUniformLocation incorrectly, which could account for "sometimes it works, sometimes it does not".

I haven't used glium before (I've been making some graphics applications directly off of Vulkano for a while). However, perusing the API, it seems you can get your Window handle from winit by going through a series of apis. I outlined them in the below code. Something like the below should work for you. The key is getting access to the Window handle from winit. Scrolling through the Window API you should see this: request_redraw. You can then insert game-loop logic around your event handler like this:

In your situation fastest fix would be to add nodesep = 0.15 graph attribute (right after digraph { statement). This attribute adjusts the minimal distance between the nodes in one rank. This results in:

Also you may play with headport and tailport attributes, as I suggested in the comment. Shortcut for them is to add a colon after node when you are defining edge.

If you replace TR_Client_Data -> idle with TR_Client_Data -> idle:e you will get this result:

Edges are crossed, but they are apart.

Also I've noticed that you define node attributes in a wrong way: keyword node defines global attributes for all nodes in the graph (or subgraph). If you want to specify attributes for a single node, place them after node definition.

e.g.

WRONG:

It looks like I missed installing some dependencies.

sudo apt install pkg-config libasound2-dev libssl-dev cmake libfreetype6-dev libexpat1-dev libxcb-composite0-dev

https://github.com/amethyst/amethyst#debianubuntu