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.

Sign up for GitHub

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

Jump to bottom

Map Data aren't refreshed due to last changes to OutputParser #110

Closed
studiofuga opened this issue Apr 5, 2018 · 2 comments
Closed

Map Data aren't refreshed due to last changes to OutputParser #110

studiofuga opened this issue Apr 5, 2018 · 2 comments
Labels
bug
Projects
Interfacing DISPLACE GUI with a database
Milestone
0.10.0

Comments

@studiofuga
Copy link
Collaborator

No description provided.

@studiofuga studiofuga added the bug label Apr 5, 2018
@studiofuga studiofuga added this to the 0.9.12 milestone Apr 5, 2018
@studiofuga studiofuga added this to To do in Interfacing DISPLACE GUI with a database via automation Apr 5, 2018
@studiofuga
Copy link
Collaborator Author

This requires a change deeper than expected. It is non optimal to reload all the data from the db, so we need to signal the change somehow. A good option is to use the IPC with a new signal code that alerts the gui of the data sent to the db. This signal must be emitted after the transaction is committed.

Interfacing DISPLACE GUI with a database automation moved this from To do to Done Apr 5, 2018
@studiofuga
Copy link
Collaborator Author

This has been closed by commit 630b3ff also restoring the functionalities of OutputFileParser.
But it needs reworking to remove the overhead and the dependency by text files.

@studiofuga studiofuga mentioned this issue Apr 5, 2018
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
Interfacing DISPLACE GUI with a database
  
Done
Milestone
0.10.0
Development

No branches or pull requests
1 participant
@studiofuga