OBEX 🗿🗿🗿
Wuerfel_21
Posts: 5,218
https://obex.parallax.com/obex/
Notice how there's no way to actually click on the objects to get to their page (and I'm pretty sure you ought to be able to click on the authors, too)
@VonSzarvas
Comments
Oh the joy of running updates on a Sunday when no-one is watching :-)
Should all be back to full linkeroo !
(Although I think the author profile links only activate when you login- to prevent spam and excessive moderation)
Also the file editing thing got kinda broken/nasty. I wanted to push NeoYume V1.4, but got frustrated, so now I just put ZIP files of each version.
Guessing you are referring to the post-back redirect when deleting a file?
And this message ... "Recent file changes are being processed - try clicking the file browser refresh icon!"
Yeah - need to click the refresh icon in the download window, or the browser, then edit/upload the replacement file.
At some point we dropped back to free versions of things that didn't have the inline editing. Plus Google API limits the speed of certain operations (and async of course!)
Bugs me too and is almost top of the list to improve one rainy and quiet weekend.
Feel free to shout if you see anything else worth doing there.
I'm not sure why a google API would be needed to upload files in the first place? External APIs, especially from dumbasses like Google, are a recipe for very quick failure.
Surely this stuff isn't so large that it doesn't fit comfortably into the normal storage of the server?
And it's incredibly slow to execute too. The browser greys out for a few seconds. Probably waiting on a server response after sending all our details into the cloud.
yep. Free is not always most performant.
At what moment do you see grey? Login, upload, download, edit ?
Is there a chance that could be related to javascript blocking or some sort of filtering on your machine / network / etc.. ?
Sure it takes a moment to upload (and the progress wheel indicates that)... but I've never seen grey-out; at least don't recall noticing it.
Just had another look. It's not really any one step. It's just sluggish all the way. It dims in some places while other places it gives progress dials or bars ... for very small steps. I mean 10 kB download shouldn't be a hurdle but it acts like it's a big deal.
That bloated feel for something that has no need for scripting at all.
ok, cheers, will keep that in mind.
One place I fixed up recently was on my desktop KDE. It took me some years to figure it out. All games and benchmarks were generally reporting > 100 Hz frame rate when vsync was disabled, and 60 Hz with vsync enabled. But none of them were actually achieving reported rates. For the most part they visibly sat at 30 Hz frame rates.
The fix turned out to be disable the desktop compositing. Now I can finally see tearing with vsync off.
There's certainly something weird afoot with KWin's compositing and the overall synchronization of everything. Things that really should be smooth and fully VSynced aren't. Sometimes I get tearing with V-Sync on... I'm using the X11 session, maybe this is something fixed in the wayland version (to offset all the broken things), haven't tried that yet.
This is why messing with gaming/emulation stuff on the P2 is fun, I can hard-sync everything together with minimal latency and zero jitter.
Unlikely. From what I've heard Wayland, like Vulkan, still has some fleshing out to go yet. And compositing is likely in the same boat. ie: There is one approach completed but that doesn't suit everyone. Put them all together and you'll be in a straitjacket.
When I first heard that the Amiga's desktop GUI, named "Intuition", was also a compositing GUI (Wasn't talked about at the time), I thought yay, I remember those early days where the windowing didn't leave damage trails all over the screen when a program was too busy to repaint itself.
Sadly, legacy always gets in the way. The non-compositing "stacking GUI" seems better supported for the moment.