You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
While developing the Bambu plugin I was attempting to use the onBeforePrintStart viewmodel callback to pop my own print options modal prior to starting. If you use the load and print button from the file list the filesViewModel.selectedfile property is not populated with the file that the button was pressed from but the previously selected file if any. This means I have no way of knowing which file was selected to print.
Describe the solution you'd like
Would like to get the selected file data object (including name, path, storage, refs, etc.) added to the onBeforePrintStart callback to allow for further processing.
Describe alternatives you've considered
monkey patching filesViewModel.loadfile (probably will be my interim solution)
reordering the loadfile function to have the callbacks after file selection so that filesViewModel.selectedfile is populated prior
disabling the load and print button entirely and force selecting the file
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
While developing the Bambu plugin I was attempting to use the onBeforePrintStart viewmodel callback to pop my own print options modal prior to starting. If you use the load and print button from the file list the filesViewModel.selectedfile property is not populated with the file that the button was pressed from but the previously selected file if any. This means I have no way of knowing which file was selected to print.
Describe the solution you'd like
Would like to get the selected file data object (including name, path, storage, refs, etc.) added to the onBeforePrintStart callback to allow for further processing.
Describe alternatives you've considered
Additional context
No response
The text was updated successfully, but these errors were encountered: