|
Microsoft at it again. Power point by default breaks a word to next line so you have few letters on first line and rest on next and there is no direct way to turn off this feature ( Elephanting bug !!! ). The only way you can turn it off is...
You install an Asian Language (eq. Japanese ) from Control Panel and then in PPT you select the textbox for which you want to turn it off and select Paragraph and go to Asian Topograpy option and you can turn off the feature there. If you only have English language you don't have that option. What a software design. 
This is what you need [^]
Zen and the art of software maintenance : rm -rf *
Maths is like love : a simple idea but it can get complicated.
|
|
|
|
|
virang_21 wrote: Power point by default breaks a word to next line
Is that for sure ? Been using 2016 over a year now, and never cam across that problem- 
|
|
|
|
|
I don't use it often but I also don't recall that being a problem.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
I've just attempted to reproduce your problem and I can only do it if I deliberately shorten the input area to less than the length of an entered word ... and it "breaks" the word at the right-hand edge, which makes sense.
I'm intrigued by this. Do you have a specific example you can describe in more detail?
By the way your link is NSFW - it was blocked when I tried to look at it
|
|
|
|
|
|
The first thing that works. That's what you use. The collateral knowledge gained might be bookmarked for a later look. Forget the problem. Get up the next day. Might or might not encounter another problem and recall that it IS the same ... what was it? A problem?
This is the definition of a bad character. You do this, you're bad.
|
|
|
|
|
Chris Maunder wrote: If so do they go into this stuff or just navigate around it and give you a best-practices approach to JavaScript coding?
When I went to college I don't remember anyone teaching anything like that for the languages that they taught which included pascal and fortran.
So not sure why anything should be different now.
More so since I have since learned of course that often "best-practice" is very likely only "my opinion" when someone actually questions the source. In college though the 'source' at least sometimes was cited as some book which the teacher was the author - so often not really a viable source even then.
Chris Maunder wrote: ...as to how knowledge of these ancient arts is passed down in a way that let's people move on sanely.
By doing it day to day in a job. Certainly how the two people that I worked with in a lab in college did it. The lab certainly wasn't teaching anyone how to create an actual circuit but at that point they had been doing it for a job for about 15 years. They were only going to the university because, at that time, the only way you could move up at their company and get paid more was by getting a degree. Despite the very obvious evidence that taking the class wasn't going to teach them anything at all.
|
|
|
|
|
They didn't teach JS when I was in college (Java instead  ). Tbh I think a lot of JS confusion comes from attempting to apply how other languages work that you already know to how JS works - and it's almost always wrong. The topic that always comes to mind is this[^].
Personally I like that JS lets you have flexible control on context, use, and binding. I disliked the complexity at first but after spending some time with the language I see the usefulness on top of it being much less mysterious now. Some stuff is obsolete but some things can only be accomplished using a specific technique as the article points out.
modified 8-Feb-18 20:24pm.
|
|
|
|
|
|
 fast, powerful and easy.
GCS d-- s-/++ a- C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
I grad I'm NOT using C or C++. The day of manual memory management, its so flexible, so archaic, its such a dinosaur. I have to go back to it once in a while when developing IoT stuff, but other than that, I'm happy with C# and even JS.
|
|
|
|
|
So called 'garbage collection'. That is why apps these days are so bloated. Managing the memory yourself means you only use what you need, when you need it. It really is very simple.
|
|
|
|
|
And so called "Memory Leaks" creep up on self managed memory allocation sometime blue-screened the entire app. Or are we so perfect that it will never happens? 
|
|
|
|
|
Why would memory leak? You free memory when you have done with it.
|
|
|
|
|
where are the other 25 reasons ? curious to read those too. 
|
|
|
|
|
|
Chris Maunder wrote: Is anyone learning JavaScript at a school or college?
Sorry... we have to rephrase that as per the PM to make it 'inclusive'.
What had heretofore been known as JavaScript will now be called BeverageScript.
Office of the PM
|
|
|
|
|
BeverageKind is, I think, the accepted term.
cheers
Chris Maunder
|
|
|
|
|
|
In my experience people don't learn JavaScript.
They copy-paste random code until it magically starts working, then refactor everything into a gazillion functions and plaster unit-tests all over it. Once they realize they've written too much code and have too many dependencies, they call it a framework.
¯\_(ツ)_/¯
|
|
|
|
|
Your question almost seems to assume that those writing JS are "learning it at school or college".
My impression is there is a lot of blind use of "other" code, that is misunderstood, then f*rked, patched, etc.
Exactly what is going on in every new crypto-currency.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
Last time I heard MIT switch to JavaScript from Java. Most school teach web (authoring) and some minimal JS. When I was in school, the only teachable languages available are C, Pascal and FORTRAN.
|
|
|
|
|
|
Reason #26, and still, the page that shows the article fails to render properly on IE11.
I'm seeing the image at the top, lots of blank space, then the comments at the very bottom of the page.
|
|
|
|
|
JavaScript is such a mess that in the past few months while writing some code that should have been simple, loading configuration before starting listening for user requests, I caught myself thinking that what I was doing would have been trivial if I was writing it in C. Add a decent HTTP library or *cgi server and the rest of it wouldn't have been too difficult either.
I'm pretty convinced that no one who says anything good about JavaScript has ever even tried to read the ECMAScript specification.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
