Skip to content

Migrate to Render layers API #164

Open
Exiled1 wants to merge 14 commits intogaasedelen:developfrom
Exiled1:render_layers
Open

Migrate to Render layers API #164
Exiled1 wants to merge 14 commits intogaasedelen:developfrom
Exiled1:render_layers

Conversation

@Exiled1
Copy link
Copy Markdown

@Exiled1 Exiled1 commented Nov 29, 2025

So, while I was fixing #163 I also noticed that I could go ahead and migrate the old usage of the highlighter API to use the new RenderLayers API released with binary ninja 5.0. Although this PR is built on top of #163 because otherwise displaying coverages didn't work.

I did use AI to get up and running but it does work and is tested on Binary Ninja 5.2.8614-stable.

gaasedelen and others added 14 commits August 10, 2021 16:41
…because dockable widgets no longer are supported, need to migrate everything to a SidebarWidget
…across CoverageOverview and lighthousewidget.visible not existing, still need large changes to migrate out of dockablewidgets.
…on't need to do that though. Also render layer not displaying in layers menu
Fully completed the IL porting, however, there's still some issues with
the error message handling when we load a coverage file and there's no
Lighthouse Sidebar that's open. Everything else works though. Oh, and
there's an annoying issue with how binary ninja shows a render layer to
the user within the render layer settings.
@Exiled1
Copy link
Copy Markdown
Author

Exiled1 commented Nov 29, 2025

I wasn't quite able to come up with a good way to accomplish a force refresh of the UI, so when a coverage file is loaded for the first time it won't render the layer correctly. I don't quite know what a solution would be, there were some C++ hacks that existed with marking stuff as dirty, but it didn't work me.

https://github.com/Vector35/debugger/blob/052139fc0bd04e00a6878487a16e298bdf32f765/core/debuggerfileaccessor.cpp#L76

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants