You said unfoldable not non-compressible. Your fault.
ulterno
joined 3 months ago
This is a nice example that also makes me think more questions.
- Will the hole punching be forward or backward?
- Assuming infinite deceleration, for an observer on the other end of the barn, will the barn be punched through, before or after the pole-pusher has stopped?
- For the pole-pusher, will the barn be punched through, before or after it has stopped?
Gets more interesting
The only time any information can be encoded onto entangled particles is when they’re created.
If that were the case, then we aren't really doing FTL communication, unless we manage to entangle them at a distance. No?
OIC, it's still useful if we want to make a secret key and send it somewhere. Then both sides can take a reading sometime in the future and they can then use whatever cluster of entangled particles they saw, as the symmetric key.
People tend to say this about everything. I read someone's about Qt Documentation and that is after having learnt to do with Qt in 1 month using solely the Qt Creator's F1, that I took over 3 months with STL.
I bought an "Ant" brand keyboard recently and it had Kailh Red switches.
I don't know if that actually represents Kailh quality, but I had the switches failing from day 2. The keyboard was not 6KRO Anti Ghosting and the backlight was not RGB, just multiple colours. That's when I realised, they were probably not going to return my money.
I having been hoping to get a Cherry MX 10.0N but they don't sell to my country and I don't feel like trusting jewellery sellers on Amazon, who have listed it for 2x the price.
So just looking to find LP Speed or other similar switches, and get a board printed, to use with QMK stuff.
You only really need the socks.
The stuffed toy is for emotional support.
The Monster is to make you die before you fall into depression and can be replaced with lemonade if you'd rather see your program get obsolete.
The choker ? ... makes your corpse easier to be towed when you eventually die of Monster poisoning. So if you are going with lemonade, you can replace this with an ESD Safe Wrist Wrap, which you will need when cleaning those fans.
"New with tags" : The tags are optional. You can get your grandma to knit a better one and have some interaction while you are at it.
I called Seagate a couple years ago, asking for an official seller in my country...
They recommended Amazon :facepalm:
Oh! You actually used QDockWidget instead of making it from the start. I should have read the code before commenting, I guess.
Nice.
Depending upon what you are aiming for, I'd go with a sidebar. Something like this:
- (a) The sidebar's horizontal width can be changed, causing all docked widgets in it to resize their width to fit.
- (b) The docked widgets/sections may resize vertically, either automatically or manually
- In case of manual resizing of widgets, you might want to add a scroll area in the widget
- (c) A widget/section may leave empty area in the bottom or vertically expand to fill
- (d) In case of empty area, the sidebar can either have empty space or be vertically shortened to expose part of the workspace underneath
- (e) Instead of having just a single widget, you can have a section on the toolbar, with multiple widgets in it. In this case, when the user changes the tab, the section will either automatically resize (vertically) as per widget requirements, or will stay the size that the user set manually, adding a scrollbar in case of overflow or empty area in case of lack of widget content.
This is in contrast to usual sidebars that tend to have a main tab bar, which only allows for a single docked widget to be shown at a time. This will allow the user to stack widgets both vertically and horizontally as per their requirements. A similar example can be seen in the right side panel in the Design Mode of Qt Creator itself.
Folded widgets/sections, when docked, will yield vertical space to other widgets/sections, which will in turn, snap upwards (or you can do downwards if that's your fancy)
Maybe you can also make the floating widgets mergeable into tabs, which will reduce the number of point+click actions in cases where only 1 of 2 widgets is being used.
Somebody used the wrong rated fuse
Who needs manuals!? Download the source code! Don't RTFM. RTFSC!
The code is the documentation!
Get ed!
I realise I should have been more specific.
Considering the pusher as a point object, deceleration of the pusher be infinite. Just another simplification so that you don't have to calculate what would happen to all the speeds in between.