* partially revert #3193 - printing the terminal escape sequences directly to text widget causes more issues than the tab problem it tried to fix
* move the conversation to html from command task to the console widget
* add hack converting tab to multiple spaces
the output of rizin was formatted as html, which caused \n to become
<br/>, making it impossible to just use appendPlainText() as-is. We have
to tell rizin not to give us html, so that we can use \t in the output.
Simply replacing \t with spaces, ` ` or similar doesn't work, as
the appendHtml() replaces multiple spaces with one.
* Fix plugins paths for windows builds due recent changes in rizin
* Disable openssl support for yara win
* Disable use_sys_yara in linux/osx/win builds
* Keep scroll history in decompiler widget.
This commit adds a `scrollHistory` on top of the rizin-managed
history, that keeps track of the scroll position within decompiled
functions.
* Fix clearing history upon init.
This commit adds support for a `topOffset` history (on top of the
rizin-managed history), that keeps track of the offset of the top
instruction in the disassembly widget.
closes#2970
Adds Quick Filter and generic address-based context menu entries to the
existing ClassesWidget. The original ClassesWidget.ui is not used
anymore as the layout is provided by ListDockWidget and only adjusted.
The AddressableItemContextMenu may now also optionally be shown when
there no currently selected item by using
setShowItemContextMenuWithoutAddress(). This is used e.g. to display the
"Create Class" option when nothing is present in the list.
Fixes#2237
Co-authored-by: Tristan Crawford <tristanthtcrawford@gmail.com>
In the TypesWidget, right-click+Load New Types was opening the dialog
for editing an existing type instead of creating a new one. This would
either result in an error (for atomic types) or the old type being
deleted on success.
* Updated GraphGridLayout documentation
* Don't use potentially misleading name "segment tree" .
Not exactly segment tree (although sometimes called that), and for the purpose of high level understanding how graph layout works doesn't matter what it is. Any data structure which provides required queries could be used.
Co-authored-by: Kārlis Seņko <karlis3p70l1ij@gmail.com>
This fixes a double-free in getSignatureInfo() when the string was
already freed by the intermediate CutterJson. But actually just using
this CutterJson makes more sense than the string anyway, so let's do
that.
The old JsonModel rebuilt the entire structure, defeating the main
purpose of a custom model in comparison to the existing QTreeWidget.
And since we are holding the json structures ourselves anyway, such a
custom model does not have many benefits anyway.
