|
Ok.
I now got it, the animation is actually an extern file (i.e. *.WebP) so you can't jump to "the last line" of it.
Forget it then...
-------------
The final slide would be more a sort of "BOOL execute once = TRUE", you don't need to make the "end slide" because this is responsibility of the user. But if I were going to use it, I would like to be sure that a not planed click doesn't start it over again... that could look a bit unprofessional depending on the audience. So the "execute once" would be a nice thing to avoid it.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Nelek,
Thank you for the clarification.
Nelek wrote: the animation is actually an external file (i.e. *.WebP) so you can't jump to “the last line” of it...
Not quite. The animation comes in several ways: 1) animated bitmap file (for example, multi-layered (animated) .webp, 2) animated SVG, 3) just video, such as .WebP, that is, any media files, representable by a browser. If the video frame type is specified, it is done not directly, but by placing in a standard <video> element. Therefore, all these presentation frames (not to be confused with video frames) could be navigated to the next or previous presentation frame, at any time.
But that's not all. The presentation doesn't have to be an external file. Also, it could be some HTML section, identified by the system by some simple rules, and that HTML fragment can be either static or it can use CSS animation. But CSS-animated HTML content is nothing more than just a state of a Web page, so it also can be navigated to the next or previous presentation frame. In fact, during the presentation, no one can even see the difference in the nature of the presentation frames. The only exception is the characteristic look of a <video> element with its well-known controls, but only it is not operating in a full-screen mode.
I would say, all the power I see in this approach is its uniform behavior of all frames, no matter what is their nature.
Thank you for the discussion again. I'll greatly appreciate any notes, ideas, suggestions, and especially any criticism.
Thank you.
—SASergey A Kryukov
|
|
|
|
|
|
Sergey Alexandrovich Kryukov wrote: Thank you again for the typo reporting!
You are very welcome
Sergey Alexandrovich Kryukov wrote: I also credited your reporting in both articles.
Thank you, although it would not have bothered me not to. At the end was only a typo, nothing technical.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Nelek wrote: At the end was only a typo, nothing technical.
Even though it is true, there are some unwritten rules of politeness in publications.
Thank you.
—SASergey A Kryukov
|
|
|
|
|
OK. Then I will just say "Thank you" and shut up 
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Sergey A Kryukov
|
|
|
|
|
A long time back, I used to use this strategy:
First 20 percent of the presentation (in terms of duration) - What we're trying to solve, motivation, introduction. Basically setting the context.
Next 60 percent - The content proper, all the stuff you want to present. This is the core of the presentation.
Last 20 percent - About what we just discussed/solved. Conclusion. Can include a short quiz to test audience attentiveness, and give chocolates as gifts. This is one way to make them remember your presentation for long.
Numbers can vary. For example it can be 25 - 50 - 25. Or even 33 - 33 - 33 in the extreme case.
|
|
|
|
|
Death By Presentation is alive and well!
Presentations turn people off. Get them round a big table and have a conversation instead.
|
|
|
|
|
Based on the military idea of tell them what you're going to tell them, tell them, tell them what you told them?
|
|
|
|
|
No idea. I haven't had to give a presentation since I graduated college (1992).
These days, I write a document and send it out to the people who need it, and ask them to send me back any questions they may have for clarification. I never receive any questions. I doubt they even read the document. But I think they are grateful for not having to attend a presentation about something they don't care about.
Similarly, whenever I receive a meeting invite, I ask the sender to send a document I can read before the meeting. They never do, and I never attend the meeting.
[ Insert quip about meetings being like Socially Transmitted Infections -- no one want to get one, no one wants to give one. ]
|
|
|
|
|
Depends on the presentation and audience.
I once had to do a 10 minute presentation about myself and my company to my peers in an informal setting.
Doing things differently was encourages.
I started like this:
"Hi, I'm Sander Rossel and I'd like to start at the beginning.
It all started 13 billion years ago [slide of some cosmic big bang].
I'm looking at the time so I'm going to skip some slides [skips slides of dinosaus, stone age, a medieval setting, second world war, ends on a slide of me and the year 1987].
So stuff happened and then it was 1987, a very important year because that's the year I was born."
And from there the actual presentation started.
This small joke (took about 10 seconds I guess) had the audience laughing and wanting more.
I put a few other jokes in there too.
This was a weekly meeting with about 20-30 business owners and we had a presentation like this every week.
Guess which one everyone remembers.
Not saying you should become a stand up comedian though, it would be out of place if you're presenting your product to potential customers, for example.
But try to find something to make you stand out and to immediately captivate your audience.
Also, keep your sheets minimal.
If there's too much text, people will (try to) read the sheets and they can't read and listen at the same time.
At the end, people will forgot what they read and they won't have listened to you.
So, say features of your product are sales and stock, list them as such:
Features:
- Sales
- Stock
Rather than:
Features:
- Sales, a module for making, and keeping track of, sales orders
- Stock, a module for keeping track of real-time stock.
You have to explain that last bit.
Also, don't read from your slide or a piece of paper.
Practice a dry run in front of the mirror at least three or four times and then again a day later.
The more natural you come across the better it will stick.
Hope that helps!
Good luck! 
|
|
|
|
|
Record yourself talking so you pretend you're hearing yourself. If you're not engaging to yourself, you won't be to others.
Practice telling it to yourself. If you're nervous or have the jitters, you'll lose the audience no matter how good the story is.
If you're funny crack a joke. If not, don't. Self-awareness is key.
Always have a character arch, plot twist, etc. Even short stories shouldn't move in a straight line where peeps know how it's going to end from the start.
Jeremy Falcon
|
|
|
|
|
What will be the actionable intelligence (ai) that you are trying to offer, and do you expect folks to gather that (ai) from what you say, or what they will read, when they get a copy of the slide deck?
If you know those things, clearly, and concisely, then you have a chance. However you also need to know what the readers, listeners, and attenders of the presentation want to hear - what is their particular 'doubt' that you need to address.
Now you have a proper handle on the importance and priority of just how good your story needs to be. In some cases it's just a place holder so you can pick it up later, other times it's a 'now or never' commitment.
Plenty of preparation prevents p*ss poor performance!
|
|
|
|
|
It is all about the audience and the message you are trying to convey. What you say and how you say things to a group of developers is much different than mid-level management. The terms you use and the level of detail needs to be appropriate for the people that will consume it.
So, start with the point you are trying to convey. Then ask what is a meaningful way to talk about that point to the audience. That will get you going in the right direction.
Good Luck!
|
|
|
|
|
|
How it helps the business/ end user succeed.
How much money it saves(productivity) or generates in new business revenue.
How little it cost to implement in relation to previous items.
|
|
|
|
|
I have a few little simple data structures in C++ that don't rely on the STL. They're exception free and meant primarily for embedded and IoT.
My simple_vector<> had a clear() function that removed all elements but no erase() function that would remove a range of elements.
Related background: I ran into a performance issue in my UIX library in the dirty rectangles routine.
Basically the issue had to do with dirty rectangles being put into the list that were already covered by another rectangle in the list, causing UIX to draw the same area(s) twice in some situations.
Sometimes this wasn't a problem, as upon insert I collapse already contained rectangles without adding them, and merge intersecting rectangles into one larger rectangle.
However, there are situations where this isn't enough. What if you invalidate two dirty areas, creating two rects, and then invalidate the whole screen? One rect will have been consumed by the merging process but the second one has nothing to combine with.
Enter the erase() function. My vector never needed one prior, because it's not a general purpose container, but rather a specialized/streamlined subset of a general vector meant for scalar data types only, and it was only being used in a certain way.
I keep back propagating features into dependent libraries when I need something in my main lib, like htcw_uix relies on htcw_data, so as above when htcw_uix needed that feature I went back and added it to htcw_data and I'm not sure I like that, as it speaks to incomplete design? maybe. or maybe this is just the natural progression of iterative improvements in my codebase and I'm being too finicky about how it comes about.
In any case, I'm probably overthinking it. But you should see my dependency tree for my major projects.
In fact, here:
codewitch-honey-crisis/htcw_gfx @ ^1.636
codewitch-honey-crisis/htcw_bits @ ^1.0.7
codewitch-honey-crisis/htcw_data @ ^1.0.9
codewitch-honey-crisis/htcw_io @ ^1.1.43
codewitch-honey-crisis/htcw_ml @ ^0.1.3
Those are just for my graphics library, which is the lone dependency of my user interface library, htcw_uix.
Anyway, those dependent libraries only really get changed if I find bugs or if htcw_gfx or htcw_uix require them to be.
Like I said, I don't know if I like that. Part of me thinks I should go through and round out some of the features in these libraries. Part of me thinks that's feature creep. All of me thinks I'm overanalyzing it. 
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
honey the codewitch wrote: What if you invalidate two dirty areas, creating two rects, and then invalidate the whole screen? One rect will have been consumed by the merging process but the second one has nothing to combine with.
Wouldn't invalidating the whole screen would be a special case where you don't care about the list of invalidated rect's?honey the codewitch wrote: Part of me thinks I should go through and round out some of the features in these libraries. Part of me thinks that's feature creep.
KISS and YAGNI would seem to apply here.
Software Zen: delete this;
|
|
|
|
|
Gary Wheeler wrote: Wouldn't invalidating the whole screen would be a special case where you don't care about the list of invalidated rect's?
Yes, but I was using that example as illustrative of the general problem, which remains.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Hi,
For the past two days Microsoft Defender dislikes the daily build mail, saying it has a "Exploit:Win32/CVE-2017-11882!ml".
Anyone else got this or is it just my Outlook+Defender that are misbehaving?
Note: going through the browser webmail and opening the mail doesn't show any problem...
Any ideas would be welcome...
|
|
|
|
|
I run defender and it doesn't seem to affect me? I'm not on outlook yet, but Microsoft is about to force me onto it. 
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
It's very possible, that it only happens on Outlook: Defender complains about an attachment file in the temp folder (sorry, should also have posted this info).
And it's not impossible that it's only in my pc: the email server is in a VM and has an Outlook Plugin that simulates an exchange server. It's possible that this plugin does something different than standard Outlook.
|
|
|
|
|
carloscs wrote: the email server is in a VM and has an Outlook Plugin that simulates an exchange server. It's possible that this plugin does something different than standard Outlook.
"Simulating" an Exchange server is no small feat, I agree with your suspicion that this plugin is doing something incorrectly.
|
|
|
|
|
I have Outlook running against Exchange OnLine and have had no issues.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
