hotkey to restart simulation and related stuff
![beep_doop](https://simulide.com/p/storage/ultimatemember/2186/profile_photo-80x80.png?1725762085)
Quote from beep_doop on June 19, 2024, 6:35 pmit would be good for productivity to have a keyboard shortcut to restart the simulation on a keypress
i use an external editor and compiler, so i want to alt-tab into simulide after compiling and press a key to reflash and restart the simulation
this eventlistener seems to do theĀ trick:
void MainWindow::keyPressEvent( QKeyEvent* event) { int key = event->key(); if( key == Qt::Key_F5 )CircuitWidget::self()->powerCircOn(); }
it would be even cooler if it was possible to send messages to Simulide from external processes to do this and maybe other stuff too
example use cases could be:
- simulating complex computer <-> device communication
- integration to external debugger
- automatically setting various states for the simulation
I think named Pipes (Windows) / FiFo files (Linux) would be a good approach,
maybe also shared memory.
it would be good for productivity to have a keyboard shortcut to restart the simulation on a keypress
i use an external editor and compiler, so i want to alt-tab into simulide after compiling and press a key to reflash and restart the simulation
this eventlistener seems to do theĀ trick:
void MainWindow::keyPressEvent( QKeyEvent* event) {
int key = event->key();
if( key == Qt::Key_F5 )CircuitWidget::self()->powerCircOn();
}
it would be even cooler if it was possible to send messages to Simulide from external processes to do this and maybe other stuff too
example use cases could be:
- simulating complex computer <-> device communication
- integration to external debugger
- automatically setting various states for the simulation
I think named Pipes (Windows) / FiFo files (Linux) would be a good approach,
maybe also shared memory.
![arcachofo](https://simulide.com/p/storage/ultimatemember/2/profile_photo-80x80.png?1725762085)
Quote from arcachofo on June 20, 2024, 9:15 amit would be good for productivity to have a keyboard shortcut to restart the simulation on a keypress
i use an external editor and compiler, so i want to alt-tab into simulide after compiling and press a key to reflash and restart the simulation
this eventlistener seems to do the trick:
void MainWindow::keyPressEvent( QKeyEvent* event) { int key = event->key(); if( key == Qt::Key_F5 )CircuitWidget::self()->powerCircOn(); }
Yes, a shortcut for restarting the simulation can be useful.
Will you do a PR?
it would be even cooler if it was possible to send messages to Simulide from external processes to do this and maybe other stuff too
example use cases could be:
- simulating complex computer <-> device communication
- integration to external debugger
- automatically setting various states for the simulation
I think named Pipes (Windows) / FiFo files (Linux) would be a good approach,
maybe also shared memory.By now I don't see any use case that justify implementing something like this.
I think this should be discussed in relation to some particular use case.
it would be good for productivity to have a keyboard shortcut to restart the simulation on a keypress
i use an external editor and compiler, so i want to alt-tab into simulide after compiling and press a key to reflash and restart the simulation
this eventlistener seems to do the trick:
void MainWindow::keyPressEvent( QKeyEvent* event) { int key = event->key(); if( key == Qt::Key_F5 )CircuitWidget::self()->powerCircOn(); }
Yes, a shortcut for restarting the simulation can be useful.
Will you do a PR?
it would be even cooler if it was possible to send messages to Simulide from external processes to do this and maybe other stuff too
example use cases could be:
- simulating complex computer <-> device communication
- integration to external debugger
- automatically setting various states for the simulation
I think named Pipes (Windows) / FiFo files (Linux) would be a good approach,
maybe also shared memory.
By now I don't see any use case that justify implementing something like this.
I think this should be discussed in relation to some particular use case.