Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Request] Macro Construction #138

Open
MediaMerge opened this Issue Mar 7, 2019 · 6 comments

Comments

Projects
None yet
2 participants
@MediaMerge
Copy link

MediaMerge commented Mar 7, 2019

The ability to create a macro that assembles multiple packets to various addresses via UDP or TCP into a stack with an assignable delay time between each (ideally in milliseconds). And then to be able to click a button to generate a desktop link that will execute the macro in the background when needed.

@dannagle dannagle self-assigned this Mar 7, 2019

@dannagle dannagle added the enhancement label Mar 7, 2019

@dannagle

This comment has been minimized.

Copy link
Owner

dannagle commented Mar 9, 2019

I really like the script generator idea. That has the added bonus of clearing up confusion people have with the command line version.

@dannagle

This comment has been minimized.

Copy link
Owner

dannagle commented Mar 9, 2019

I am thinking of a tool to generate a .bat or .sh file based on saved packets that can be double-clicked and edited by the user once generated.

@MediaMerge

This comment has been minimized.

Copy link
Author

MediaMerge commented Mar 11, 2019

You might need to test the sleep command... seems like I remember that basically locks the computer down until it expires.

A .bat file seems the path of least resistance though they have drawbacks. Since this is something (in my use) that would be left for an end user I'd prefer it really clean, running in the background with no sign of a command window or a way the user could interrupt it.

@dannagle

This comment has been minimized.

Copy link
Owner

dannagle commented Mar 11, 2019

I assume you are running Windows. It is very difficult to prevent the command prompt window from appearing when run console commands in Windows. A standard way is to create a .VBS script as a launcher to the .bat. Yes, it is awkward.

Another approach is to have GUI-based .exe (instead of the command-based .com version) smart enough to accept parameters to execute a series of commands (including non-blocking sleeps). It won't show the GUI, but since we are launching the GUI version anyway, we may as well have it show a simple progress bar until it finishes and self-exits.

@MediaMerge

This comment has been minimized.

Copy link
Author

MediaMerge commented Mar 11, 2019

Could you have the smarts of the GUI running as a service to be accessed in the background as needed? Or just a subset service to achieve the needed I/O part? Just thinking out loud...

@dannagle

This comment has been minimized.

Copy link
Owner

dannagle commented Mar 11, 2019

You don't want an always-running service (especially a TCP server) if the command is going to be invoked by double-clicking an icon. That's wasting a lot of CPU cycles.

It's not a biggie to add smarts to the GUI component triggered by a shortcut. If I did it this way, Mac and Linux could potentially use this new feature too. Packet Sender gets a fair number of Mac and Linux downloads, and I'd like to keep supporting them with each new feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.