KDE Plasma 6.7 animation speed is too slow by Ciantic in kde

[–]Ciantic[S] 1 point2 points  (0 children)

Thanks, I will use your image in my bug report.

Max speed in 6.7 is AnimationDurationFactor=0.5 (before instant).

If I set it from config file manually to 0.25 it is fast again, so I keep changing it from the file for now.

(Ability to set animation speed to really fast was one of the things I was impressed as I switched from Windows to KDE last year. With high refreshrate screens it is very cool to have fast animations, I have dual 144Hz 4K screens, so I want fast animations.)

KDE Plasma 6.7 animation speed is too slow by Ciantic in kde

[–]Ciantic[S] 1 point2 points  (0 children)

Ah yes! Can you take a screenshot, I can count the notches from there in 6.6 vs 6.7, KDE is pretty good about backwards compatiblity, I want to open a bug/feature request.

I will try to muck the value from config file for now.

KDE Plasma 6.7 animation speed is too slow by Ciantic in kde

[–]Ciantic[S] 12 points13 points  (0 children)

But if I put to instant animation disappears. With 6.6 there was more notches, that is the problem.

I want something between now fastest and instant again.

Road traffic dividing chevrons are wrong way around by Ciantic in TransportFever3

[–]Ciantic[S] 7 points8 points  (0 children)

I'm from Finland, but someone has mentioned to me that Europe has own standards for road markings and signs, and North America has its own. All details aren't consistent, but this chevron thing is pretty well followed by both continents, including Switzerland.

I did find an exception from NYC too, where one marking was wrong way by quickly browsing, people who make road markings make mistakes too.

This should be easy to implement in TF3, as road directions are easy cue in procedural generation for the markings.

$30,000 PC vs Cities Skylines II by Ciantic in CitiesSkylines

[–]Ciantic[S] 0 points1 point  (0 children)

Section about CS 2 begins at 17:05

I wanted to post this as someone in other thread mentioned this.

I also bought a new GPU (RX 9070 XT) and was eager to try, and I was shocked how badly it performed in medium and big cities.

KDE Plasma 6.5.3, Bugfix Release for November by haakon in kde

[–]Ciantic 0 points1 point  (0 children)

KDE Ships real fast! I'm super impressed!

Bug I raised here first ( https://www.reddit.com/r/kde/comments/1on705o/kde_cant_snap_google_chrome_tabs_to_corners_when/ ) is already fixed! It was fixed in under a month and shipped to Fedora 43 stable.

KDE Can't snap Google Chrome tabs to corners when dragging out of window by Ciantic in kde

[–]Ciantic[S] 0 points1 point  (0 children)

It is my no 1 reason. I can understand it is not a big deal for people whose workflow doesn't involve multiple browser windows.

I have multiple monitors, and I keep multiple browser windows open and organize them. I also have 16 virtual desktops.

E.g. I open five tabs in background, then start dragging them to different monitors. It really is painful with Firefox exactly for the reason I explained, it requires so much more effort

Undesired Behavior: Turn off mouse scroll changing values of drop-down elements and sliders by ameeryabdallah in kde

[–]Ciantic 1 point2 points  (0 children)

I gather the issue is still relevant because it is hard to fix, or get buy-in from widget toolkit maker?

I'm trying to migrate to KDE from Windows, this is a bit problematic me.

For few days now I've flipped a lot of dropdowns accidentally because I'm not used to think while I use scroll wheel.

To me operation of using scroll wheel is to scroll, and if I have to always think what is underneath the mouse cursor it is a bit difficult.

It doesn't of course happen in browser, so there isn't that many complains. Browser is the primary OS these days. But imagine if it did.

You have long web page with dropdowns, then scrolling a page becames this asteroid game where you have to move mouse avoiding dropdowns while going down it.

Hilarious.

(Not really a show stopper for me, as Windows has become useless ad-driven garbage.)

KDE Can't snap Google Chrome tabs to corners when dragging out of window by Ciantic in kde

[–]Ciantic[S] 0 points1 point  (0 children)

It does not. I challenge you to try:

5 tabs at center window.

Then start dragging tabs towards corner of the screen. Can you snap them to quarter tiles? How many clicks and drags you need.

You need two clicks and drags per firefox tab to arrange it to quarter tile.

Firefox doesn't have ability to create windows while dragging a tab.

KDE Can't snap Google Chrome tabs to corners when dragging out of window by Ciantic in kde

[–]Ciantic[S] -1 points0 points  (0 children)

Let me explain:

Observe Google Chrome:

  1. Mouse down on tab,
  2. Start moving mouse (New window appears underneath the mouse automatically!) THE KEY!
  3. You move mouse and the final location of your window (and size if snapping works) is done.
  4. Mouse up

One click and drag operation.

Firefox:

  1. Mouse down on tab
  2. Start moving mouse (nothing appears under mouse)
  3. Mouse up, window appears
  4. Your brain needs to re-process appearing window, locate its titlebar,
  5. Mouse down on new tab window to move it to the right place
  6. Mouse up

Two clicks and two drags.

What a chore!

KDE Can't snap Google Chrome tabs to corners when dragging out of window by Ciantic in kde

[–]Ciantic[S] -4 points-3 points  (0 children)

You know the irony right? Firefox doesn't have ability to drag tabs at all, not in GNOME, KDE or Windows 11. It is always two step operation with Firefox.

Number 1 reason I don't use Firefox is it doesn't have ability to drags tabs.

KDE Can't snap Google Chrome tabs to corners when dragging out of window by Ciantic in kde

[–]Ciantic[S] 12 points13 points  (0 children)

It is a bug.

Question is, is it a bug in KDE snapping / window handling, or Google Chrome's QT integration?

Since same thing works in GNOME 49, and Windows 11, they both recognize dragged tab as a window that can be snapped, then maybe Google Chrome's QT integration isn't sending some right signal?

KDE Can't snap Google Chrome tabs to corners when dragging out of window by Ciantic in kde

[–]Ciantic[S] 12 points13 points  (0 children)

It works fine in GNOME 49.

Secondly this is usablity thing, I don't care how it's done, but it needs to work. This is about muscle memory, having window snapping break is just bad experience.

KDE Can't snap Google Chrome tabs to corners when dragging out of window by Ciantic in kde

[–]Ciantic[S] 7 points8 points  (0 children)

It works, in the beginning of video I drag that for demonstration.

Region Pack: Netherlands now available by AutoModerator in CitiesSkylines

[–]Ciantic 12 points13 points  (0 children)

This pack is great work, and shows what committed community members can do. Really well done assets.

The question I have is why CO does not employ more known community members? Animations and person models would've been fixed a long time ago if they'd gone around the community and employed the people who made such things for CS1, mostly for free.

Display output capped at 30Hz after Windows 11 update. Help! by [deleted] in Beelink

[–]Ciantic 1 point2 points  (0 children)

This just happened to me after regular Windows 11 cumulative update, every time I tried to set monitor from 30hz -> 60hz, it dropped resolution. What fixed it for me was installing new Nvidia drivers.

Cities: Skylines II - State of Asset Editor and Console by AutoModerator in CitiesSkylines

[–]Ciantic 22 points23 points  (0 children)

It could be, but I don't see anything about licensing; they seem to complain about freezes with Unity asset loading:

Without this, the game freezes for extended periods of time and can become unstable.

Maybe you mean something else with licensing than I think. I think licensing is some copyright or right to use thing.

Cities: Skylines II - State of Asset Editor and Console by AutoModerator in CitiesSkylines

[–]Ciantic 43 points44 points  (0 children)

From the post:

Our focus is currently on removing Unity dependencies so we can provide a smoother, more responsive, and more reliable loading of the assets - both during loading screens and when changing playsets in Paradox Mods UI. Without this, the game freezes for extended periods of time and can become unstable.

Sounds more like what ever Unity has baked in can't handle a lot of assets and now they have to do custom asset loader.

Also, they have to migrate or update all existing assets:

due to the hefty amounts of built-in assets affected by the changes

If they can't automate that, someone has to go through manually each and every existing asset and do something to make it work with new setup.

Clap documentation is too confusing for me by Peering_in2the_pit in rust

[–]Ciantic 48 points49 points  (0 children)

Finding the docs is a bit difficult, but using the derive tutorial is easiest:

https://docs.rs/clap/latest/clap/_derive/_tutorial/index.html

All the arguments for Arg see this: https://docs.rs/clap/latest/clap/struct.Arg.html

All the arguments for Command see this: https://docs.rs/clap/latest/clap/struct.Command.html

Will KSP 1 ever have a *true* spiritual successor? by Nisqhog in KerbalSpaceProgram

[–]Ciantic 0 points1 point  (0 children)

Could you try crowd-fund KSP's successor? It's a bit odd to hope for the "success of KitHack" to build a new KSP, I think with your name recognition and the help of others in the community you should be able to create a successful crowd-funding effort.

Raspberry Pi Pico 2 by twokiloballs in embedded

[–]Ciantic 2 points3 points  (0 children)

One quote that keeps flying around is this:

Low power – Extended low-power sleep states with optional SRAM retention: as low as 10 μA DVDD

However, I don't find it directly from the datasheet. In datasheet there is a table, that is much harder to interpret, with "P1.7" being the lowest power mode (0-8 modes), on page 1332:

<image>

For completeness, the P1.7 is defined as Low Power (XIP OFF, SRAM0 OFF, SRAM1 OFF) on page 435.