Preparation for Database integration #210
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… IDs of parts and pushing them to a database
anurnberg
reviewed
May 31, 2024
Huh, indeed. They were meant for #208 and accidentally slipped into some other commit. Changed and fixed history 😬 |
|
Notes from today's meeting:
|
This opens a dialogue for entering the module ID and whether to push the acquired information
|
This now in addition includes ...
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Preparation work for integration of the database
This integrates the registration of component IDs (via barcode scanner or manual entry) as well as the upload to a database into the assembly sequence.
The registration of component IDs can either be done in the toolbar ...
or in the assembly sequence:
When entering the IDs via the input dialogue, they are nevertheless registered in the toolbar.
The information can then be pushed to the database via the workflow (or the button in the toolbar):
The user is warned about missing information ...
... or can verify before uploading the information:
A function to actually upload the information still has to be added and can be varied from assembly center to assembly center.
On the way to this, a functionality was added in the background that makes it possible to abort individual actions, otherwise the user e.g. would have been informed that the information cannot be pushed to the DB, but either the action would be marked as "Done" and disabled or at the next click (due to the way signals are connected in Qt) the popups would appear twice.
This closes #202