73 - Mid-Month Mini Update
HTML-код
- Опубликовано: 11 сен 2024
- 73 - Mid-Month Mini Update
Normally PowerDirector 365 users expect a monthly update somewhere around the first of the month. I have no idea why this update came out around August 15, 2024 but I suspect it was to fix one or more major bugs or problems with the last update, otherwise why wouldn't they just wait to the beginning of the next month?
Whatever the reason, Cyberlink ain't talking. So here is a short video to let you know about everything contained within this "mini update".
Love the ending. I might have to borrow the Green Door!!
Oh sure, doors for rent. What next, trailers for sale or rent. Rooms to let, 50 cents.
Loved the ending. Now, unless I've missed something from previous videos, that end would make a great 'How to do' tutorial.
I was thinking the same as I was creating that ending which took more time to tweak than to create the rest of the video. But some people might think that it would be too detailed and boring while a few others would find it interesting. I'll put it on the list of upcoming projects while I'll think about.
Cyberlink are a complete mess.
Nothing new on my side..!!!!!
I knew something was strange about that update because upon restarting PowerDirector, I did not get the usual "Agree to this legal stuff" window. Instead, the program started as usual as if nothing ever happened.
It was the first time I've ever seen the program recognize that there was an update available from within the program. As I've said before, whenever I clicked on "Check for Updates" my response back was always "You are up to date". Then I'd go to CAM and it would say that there was one available. So maybe the last version 0803 fixed that. Or maybe it was never the fault of the program but something in the update procedure and notifications that the program could never recognize.
Is it possible that it took Cyberlink over 10 years to be able to make a program recognize that an update was available? I just don't remember if it worked on the real older versions or not. I have to assume that it did work properly and that maybe it was only version 22 that broke it. Even so, why would it take Cyberlink 1 year to fix something like that in version 22? Oh, I forgot, the one part-time software engineer is busy with his janitorial work.