Most solutions to automatic browser refresh for development are silly: I used the same name as the input file +. tags file, if there are no errors wxHe圎ditor should reload it and refresh the displayed tags. "if it is successful it updates the tags" Pressing the button executes the script / command passing to it the name of the file opened as the first argument, if it is successful it updates the tags, if it fails it shows the output of the execution with the error messageĪll in all it seems like a simple implementation, there's no reason why it can't coexist with plugins to recognize file types and generate tags automatically.
#WXHEXEDITOR AUTO REFRESH PLUS#
There is a button-with-dropdown that keeps the list of the last N scripts / commands executed in the dropdown, the most recent visible in the button part, plus the option in the dropdown to run a new one that opens the dialogue to choose it If I remember correctly the 010 Editor system worked like this: Could you live with those constraints? In other words, would you also be happy with an invalidation model that works in terms of fixed-width blocks, where the plugin interface gives wxHe圎ditor the ability to request redrawing fixed-width blocks in response to invalidations/modifications from users? (Typically these will be page sized, or block sized - 4KiB - 32-KiB.) I wonder if the work that is using wxHe圎ditor for can fit with this model. I am not sure how general a solution this is, or how much work it would be. wxHe圎ditor could interrogate the pg_hexedit binary to get new tags based on block-level invalidations. I get it.įor what it's worth, the ideal outcome for my pg_hexedit tool (see ) would be a wxHe圎ditor plugin interface that understands that the pg_hexedit binary outputs tags for fixed-width 8KiB blocks. This is probably why 010Editor does it that way. You can do very granular invalidations, and stuff like that. There are a lot of things that a custom scripting language would enable that are hard to get any other way, since it puts the hex editor in control. That being said, I understand where is coming from. This require to another dialog panel to configure colors also. ctrl+1 -> create tag with color stored at number 1. Might be an option is eligible to enable / disable that randomization and select one predefined color. I believe it's more useful in that way.But don't know what if user switch another file tab while opened search dialog. Don't know/sure if it solve more problem than it generates programmatically.
#WXHEXEDITOR AUTO REFRESH HOW TO#
I don't decide how to generate automated tags yet. But could use directory forms if possible.
Also I think it's bad idea due might look crowded to eye. Don't know if support for it at wxWidgets API. Not added "delete" key support for deletion, yet. Need to open another issue for that may be.
0 kommentar(er)
