The Weird and The Wonderful

Intel's CPU instability and crashing issues also impact mainstream 65W and higher 'non-K' models — damage is irreversible, no planned recall | Tom's Hardware[^]

29-Jul-24 1:26

Ron Anders29-Jul-24 5:02

Ron Anders

29-Jul-24 5:02

Whew, I got out of the computer support biz just in time. First crowdstrike, now this.
All we ever had to deal with was the old intel floating point debacle.

Daniel Pfeffer30-Jul-24 12:35

Daniel Pfeffer

30-Jul-24 12:35

Intel can't afford to recall all of the chips it has produced in the last 2 years. OTOH, not recalling the chips gives them an incredible image problem.

I have bought Intel CPUs for the last 45 years (going back to my first IBM "portable" PC). It is likely that my next PC (or portable) will have an AMD chip.

Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.

RickZeeland30-Jul-24 18:36

30-Jul-24 18:36

Luckily the Dell Inspiron 16 notebook that I recently bought (for a ridiculous low price) has an AMD Ryzen 5 processor. I'm pleased with it so far, although it does not have a dedicated graphics card I can even play Skyrim on it, the fans start blowing loudly after about 10 minutes though now it's summer $Shucks | :-\$

When a UI designer chooses to use a numeric up/down when a checkbox would make more sense

Nelek30-Jul-24 22:29

Nelek

30-Jul-24 22:29

I have an AMD 5800x and an AMD 6900XT (almost three years old).

A VM, 3 Instances of "Lord of the rings" online, several browser tabs and 2 instances of Sketch up 2017 open.
Be Quiet case with 2x silent wings and a dark rock pro 4 for the CPU.
The fans only activate second speed from time to time for 10 or 15 seconds.

My first AMD components and, right now, I do not see me coming back to intel soon.

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.

PIEBALDconsult28-Jul-24 17:10

PIEBALDconsult

28-Jul-24 17:10

I really really don't want refried beans with my enchiladas, gracias.

https://www.codeproject.com/Uploads/Membership/Uploads/2587207/BadUIboolean.png[^]

Re: When a UI designer chooses to use a numeric up/down when a checkbox would make more sense

RickZeeland28-Jul-24 21:12

Re: When a UI designer chooses to use a numeric up/down when a checkbox would make more sense

28-Jul-24 21:12

He probably meant the number of beans you did not want $Shucks | :-\$

Mike Hankey29-Aug-24 4:34

Mike Hankey

29-Aug-24 4:34

no bueno

A home without books is a body without soul. Marcus Tullius Cicero
PartsBin an Electronics Part Organizer - Release Version 1.4.0 (Many new features) JaxCoder.com
Latest Article: EventAggregator

CSS & Sophocles, more related than you know

raddevus22-Jul-24 12:22

22-Jul-24 12:22

While working on a SPA I had some CSS that I was applying on the click of a button.
When the button was clicked, it would make one or the other DIVs go fullscreen (except for a small portion at the top where the nav bar was).

Imagine you have these two divs -- one yellow and one cyan;

CSS

#first{
  background: yellow;
}

#second{
  background: cyan;
}

Then when you click a button in the navbar it would make one or the other go fullscreen by applying a fullscreen CSS class.
It worked great & I was very happy with the simplicity of it all.
If you really want to see it work (toggle), take a look at this simple jsfiddle[^].

CSS

.fullScreen{
  width: 100%;
  height: 90%;
  z-index: 20;
  position: absolute;
  top: 12%;
  padding: 10pt;
}

Here's the button click code.

JavaScript

// select the div and add the style
document.querySelector("#first").classList.add("fullScreen");
// remove style from other div so it isn't fullscreen
document.querySelector("#second").classList.remove("fullScreen");
// vice versa for the other div -- not showing all the toggle code

It Worked, Then Didn't!
It was all working. I copied the code to another project and had it all set up.
But suddenly clicking the button wouldn't do the fullscreen. I tried all manner of things.
Was the button click working? I added an alert() and saw the button was working.
I was going out of my bleedin' mind.
Then I looked real hard at the styles that I had copied to the new project.
Can You See It?
Do you see the problem?

CSS

#first{
  background: yellow;
}

#second{
  background: cyan;
};

.fullScreen{
  width: 100%;
  height: 90%;
  z-index: 20;
  position: absolute;
  top: 12%;
  padding: 10pt;
}

Oy!! I have only myself to blame.

As Sophocles said:
The keenest sorrow is to recognize ourselves as the sole cause of all our adversities.

Sophocles was obviously a software developer.

Jeremy Falcon22-Jul-24 14:19

22-Jul-24 14:19

raddevus wrote:
Do you see the problem?

Don't see the reason for it off the top of my head. Absolute should work with a static parent. Usually when stuff is not shown and it's not a display issue (or no content) then it's related to height. As body height needs to be set as well, etc. So that would be my guess.

Couple points about your code though...

I urge you to consider never, ever doing that again though. Laugh | :laugh:

You don't need to hard code offsets, as that'll just make things harder to maintain. And, this day and age we should be using flexbox for layout. And yes that includes fullscreen dialogs. It'll keep things organized sooo much better and if you ever need to stack a dialog on top of your main content or stack multiple dialogs, then it'll make your life easier.

Also, never, ever use height 100% in that manner. Smile | :)

There are better ways now. That was the trick 20 years ago. These days it's much, much better to use viewport units for layout. Height 100% means 100% of the parent. That trick only only worked when you set both the html and body tag to height 100%. I still set both html and body out of habit for viewport, but there's no need for that now. Just use viewport units with the added benefit of being semantic.

Also, consider using the semantic dialog tag. It'll fall back to a regular div on non-supported browsers. But if the intent is to have a fullscreen dialog show, then it'll help screen readers know what's up.

Tossed together a fiddle for poops and giggles. Clickety

Jeremy Falcon

modified 22-Jul-24 20:31pm.

raddevus23-Jul-24 2:44

23-Jul-24 2:44

Wow, thanks for the tips. I really appreciate it.
I was just going for the absolute quickest way I could get a div to go fullscreen.
I will examine the JSFiddle more closely and make some changes.

Thanks again.
Thumbs Up | :thumbsup:

Jeremy Falcon23-Jul-24 6:47

23-Jul-24 6:47

Any time, buddy.

Jeremy Falcon

Jeremy Falcon23-Jul-24 7:02

23-Jul-24 7:02

Just checked the fiddle again and there was a tiny bug in it with the hidden style. If the dialog tag is supported then most browsers apply an automatic user agent style to it. So, forgot to add padding and margin resets in the class.

This fixes it: Clickety. So should work if you apply the hidden class to either the popup or the main tag.

It's worth noting this isn't an modal or modeless overlay dialog anymore, but quite literately replaces the main content while still allowing for having a nav bar up top. If it were an overlay that just covered the whole thing (drop shadow etc.) then absolute positioning is the way to go. But, IMO overlays don't look nearly as modern as this does.

Jeremy Falcon

modified 23-Jul-24 15:27pm.

raddevus23-Jul-24 7:16

23-Jul-24 7:16

Thanks, I forked it and got to this which works for my needs[^].
I just need to "fullscreen" a div if the user wants to so the div can be seen / interacted with more easily on a phone.

Jeremy Falcon23-Jul-24 9:13

23-Jul-24 9:13

Noice

Jeremy Falcon

RickZeeland22-Jul-24 19:13

22-Jul-24 19:13

Not a Javascript programmer, but I guess the extra semicolon?

raddevus23-Jul-24 2:43

23-Jul-24 2:43

You got it!

It was the semicolon located after the second style.

That just blew my mind! I will make no more mistakes with semicolons (he said doubting himself). Roll eyes | :rolleyes:

CSS

#first{
  background: yellow;
}

#second{
  background: cyan;
};  /* <=============  this semicolon makes the .fullScreen ineffective!!!! */

.fullScreen{
  width: 100%;
  height: 90%;
  z-index: 20;
  position: absolute;
  top: 12%;
  padding: 10pt;
}

Jeremy Falcon23-Jul-24 6:50

23-Jul-24 6:50

Ha ha ha ha ha. I totally missed that. Awesome catch.

Jeremy Falcon

Peter_in_278022-Jul-24 20:27

Peter_in_2780

22-Jul-24 20:27

Be thankful it's CSS not Python.
Then your bug would be invisible.

Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012

TNCaver23-Jul-24 10:22

TNCaver

23-Jul-24 10:22

I have similar code I used to swap between dark and light theme css file, selected via a checkbox:

JavaScript

function switchCssMode() {
    var chkMode = gebi("chkSwitchTheme");
    if (chkMode.checked) {
        document.querySelector("link[href='css/lite.css']").href = "css/dark.css";
    }
    else {
        document.querySelector("link[href='css/dark.css']").href = "css/lite.css";
    }
}
function gebi(el) {
    return document.getElementById(el);
}

There are no solutions, only trade-offs.
- Thomas Sowell

A day can really slip by when you're deliberately avoiding what you're supposed to do.
- Calvin (Bill Watterson, Calvin & Hobbes)

Richard Deeming23-Jul-24 21:25

Richard Deeming

23-Jul-24 21:25

For modern browsers, you could do that without any JavaScript. Set up the colours to use as CSS variables / properties[^] in the :root context; use those variables throughout the stylesheet; and use the :has selector[^] to switch between dark and light themes. Smile | :)

CSS

:root {
    --background-color: white;
    --text-color: black;
}

body:has(input[id='chkSwitchTheme']:checked) {
    --background-color: black;
    --text-color: white;
}

Demo[^]

"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer

Linux C PreProcessor: Who Knew?

TNCaver24-Jul-24 4:09

TNCaver

24-Jul-24 4:09

Interesting, and good to know. I'm way behind on modern CSS.

There are no solutions, only trade-offs.
- Thomas Sowell

A day can really slip by when you're deliberately avoiding what you're supposed to do.
- Calvin (Bill Watterson, Calvin & Hobbes)

raddevus4-Jul-24 6:26