Hi, I wonder if it's possible to add more functionally to the callbacks.
The WimGAPI has WIMMessageCallback(dwMessageId, wParam, lParam, **pvUserData)
that allows to use custom userdata and to cancel a process with returning
WIM_MSG_ABORT_IMAGE.
It there a way to do this with wimlib, too?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I've updated the progress functions in the latest v1.6.3-BETA. You can now specify a context parameter. Also, the value returned from the progress functions is now significant. Currently you can return either WIMLIB_PROGRESS_STATUS_CONTINUE or WIMLIB_PROGRESS_STATUS_ABORT.
I opted not to add a context parameter to every API that takes a progress function parameter, but rather get rid of this parameter and add a separate API (wimlib_register_progress_function()) that can be called to associate a progress function with a WIMStruct. This is similar to what WIMGAPI does, although I haven't (yet) added support for having multiple progress functions registered at the same time.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just read in the News.txt that the new version support the WimBoot feature.
I haven't used it by now, but one thing seems to be a bit unhandy, the WimBootCompress.ini needs to be inside the wim.
Maybe the apply command could accept a --config parameter just like the capture option.
So one can easily make changes to this [PrepopulateList].
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oh, have not seen this option, think it will do it.
But I just tried the wimboot apply in a VM using the current beta.
Somehow the files that are no pointer files does not get extracted, they are all 0 bytes in size.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I wonder if it's possible to add more functionally to the callbacks.
The WimGAPI has WIMMessageCallback(dwMessageId, wParam, lParam, **pvUserData)
that allows to use custom userdata and to cancel a process with returning
WIM_MSG_ABORT_IMAGE.
It there a way to do this with wimlib, too?
I will consider adding this feature. It will require some API changes.
Hi, I've updated the progress functions in the latest v1.6.3-BETA. You can now specify a context parameter. Also, the value returned from the progress functions is now significant. Currently you can return either WIMLIB_PROGRESS_STATUS_CONTINUE or WIMLIB_PROGRESS_STATUS_ABORT.
I opted not to add a context parameter to every API that takes a progress function parameter, but rather get rid of this parameter and add a separate API (wimlib_register_progress_function()) that can be called to associate a progress function with a WIMStruct. This is similar to what WIMGAPI does, although I haven't (yet) added support for having multiple progress functions registered at the same time.
Great, working nice here!
I just read in the News.txt that the new version support the WimBoot feature.
I haven't used it by now, but one thing seems to be a bit unhandy, the WimBootCompress.ini needs to be inside the wim.
Maybe the apply command could accept a --config parameter just like the capture option.
So one can easily make changes to this [PrepopulateList].
Maybe. Did you consider using the --wimboot-config=FILE option to 'wimlib-imagex update' to set WimBootCompress.ini in the WIM?
Oh, have not seen this option, think it will do it.
But I just tried the wimboot apply in a VM using the current beta.
Somehow the files that are no pointer files does not get extracted, they are all 0 bytes in size.
Apparently I broke that when changing the code. Download the v1.7.0-BETA again --- it should be fixed.