x64dbg is indeed a bit out of date when something serious like IL and decompilation is needed.
<mrexodia> Some button in the editor might work
To all beginners, if you find x64dbg difficult to use, tell me, I'll listen to your voice.
<GroupAnonymousBot> ^ @Razorrali (re @mrexodia: Official x64dbg group chat.
Rules:
Rules:
- No crack requests
- Keep it on topic (x64dbg)
- Don't PM people unless agreed upon in the group
New members violating any rules will be instantly banned.
Report a bug: http://issues.x64dbg.com
FAQ: http://faq.x64dbg.com)
<mrexodia> Not really, the language is similar but not compatible
<나쯔> thk
<Danishali123> How yo change softewere name plz help
<Danishali123> Plz
<morsisko> eg something like
while(GetMessage(&Msg, NULL, 0, 0) > 0)
{
TranslateMessage(&Msg);
DispatchMessage(&Msg);
}
<morsisko> because I don't see it anywhere, but the plugin`s dialog still get the messages, so I wonder how it works
<mrexodia> It’s in processMessage iirc
<morsisko> my question is more about the win api things
<morsisko> because normally when you, for example, create dialog in your application using CreateDialog() you need to pass the messages to the dialog with loop similar I've posted above (not sure if you messed with the winapi gui before)
<morsisko> but in case of x64dbg the loop is not needed, it look like something another is feeding the dialog queue with messages
<morsisko> not sure if it's implemented on Qt level or what, because I don't see it anywhere in the x64dbg source
<morsisko> but the message queue of my dialog is indeed filled with messages to dispatch
<mrexodia> It’s in qt
<mrexodia> But your dialog isn’t related to qt
<mrexodia> If you pump on the same thread as you created the dialog on it’ll work
<mrexodia> Or are you creating a qt dialog?
<mrexodia> So then messages will be pumped by user32
<mrexodia> CreateWindow needs a loop
<mrexodia> DialogPaeamW or whatever doesn’t
<morsisko> Ah, that's the reason
<morsisko> It's kinda strange anyway, because then the "tab" key doesn't work well, but as far as I remember it worked fine with the standard dialog
<mrexodia> Hm
<mrexodia> That is weird
<morsisko> like as now you can't use tab key inside dialog without making some strange thing like subclassing inputs that are focused
<morsisko> and I see that almost every plugin for x64dbg works like this
<morsisko> (you can't use tab to switch to the next input)
<mrexodia> It could definitely be a qt issue
<morsisko> I see that with casual event loop you need to add the "IsDialogMessage" like this:
while (GetMessage(&msg, 0, 0, 0) > 0)
{
if (!IsDialogMessage(hwnd, &msg))
{
TranslateMessage(&msg);
DispatchMessage(&msg);
}
}
<morsisko> but as the dialog got the default one, don't think there is a good way to implement this
<morsisko> but yeah that is strange, I think you can use the tab key in the native windows dialogs without any problem