Antonio Davide

Ok, I have checked the code, and yes: metadata informations are a model, so they are retained between data changes it's the intended behavior. What behavior do you want to...

Ok, it's clear. I can add that feature, but it can be very slow because the widget needs to check where the insertion/deletion happens and move every metadata that follows...

Can you test if it works by using this branch? https://github.com/Dax89/QHexView/tree/direct_renderer

> Qt 5.14.2，Compile error > >  Fixed. > [https://github.com/Dax89/QHexView/tree/direct_renderer，This](https://github.com/Dax89/QHexView/tree/direct_renderer%EF%BC%8CThis) branch also does not work, it is also unresponsive and crashes. I have checked the code and 256MB is a...

Ah ok, `setForeground()` (along with its related metadata functions) is used to highlight parts of the loaded buffer. In this case you need to use the classic Qt's `palette()` method...

Fixed, thanks for reporting it! If you can, use `direct_renderer` branch fow now, because it will get merged in the mainline branch (5.0) soon

The [last commit](https://github.com/Dax89/QHexView/commit/f6a760882ff52a2d056c91921a2175fa5d9c108f) fix this issue in a Qt6 environment, I can't test it in a Qt5 one, let me know if it's ok on your side too

So if I have understood correctly you want to highlight changes, those APIs are not meant to do that. In the last few commits have implemented changes tracking builtin in...

> not update .pri Fixed, I've missed that file. > I'd say the `trackchange_format` could be split into `trackchange_format_overwrite` and `trackchange_format_insert` respectively to further differentiate the type of changes being...

> I'd say the `trackchange_format` could be split into `trackchange_format_overwrite` and `trackchange_format_insert` respectively to further differentiate the type of changes being made. They are now implemented as `trackchange_format_ins` and `trackchange_format_ovr`