@Miakoda The worst part about the ones with welded on tabs is the price, outfuckinrageous. Some years ago at work, I found that all the laptops we had were draining the CMOS battery once the main battery died while they were in suspend-to-ram. The cost of replacing hundreds of em would have been ridiculous so we bought em in cheap packs of two. As you can see from the pictures, I fashioned me a make-shift spot welder from a large 12V battery and 15P power cord, tore all the tabs off the old ones, put some heatshrink on the new batteries and had myself a sufficiently fun day. Sharpening the prongs and bending em close together is all it took to get perfect welds nearly every time. Just a quick rocking of the plug from one side to the other, super easy.
@Miakoda So, I did manage to find mine quite easily, however, it no longer works. From what I've worked out so far, it's just the IR sensor that's tits up. I do still see all the keycodes it reports with evtest, just can't trigger em. I also found the cotroller I'd used with it in the same box, it was a XBone, not a 360 one.
I've had two old Intel PCMCIA RJ45 dongles in my toolbag for 15+ years that I rewired to be inline crossover and rollover adapters. I rewired a couple other'ns I had each with 3 RCA connectors so we could run the A/V to a second TV on the other side of the building at the shop.
Been playin around with #ComfyUI and #SDXL models for a few months now, what a fun tool. Lately I've been rather obsessed with using it to creating some ""paintings"" that I have floating around in my head. I learned most of the technique from a fella on YouTube called Rob Adams, with a bit of side reading to figure out what some of the things were I needed to play with to get what I want from his method.
I start with a basic two-tone mask that I crudely draw to give the model a main direction for the things I describe, then add a noise layer on top of it. From there it moves on to the first pass which takes an overly (#ollama) complicated series of concatenated input prompts and gives me a very rough (1024²) idea of where I'm
... Show more...
Been playin around with #ComfyUI and #SDXL models for a few months now, what a fun tool. Lately I've been rather obsessed with using it to creating some ""paintings"" that I have floating around in my head. I learned most of the technique from a fella on YouTube called Rob Adams, with a bit of side reading to figure out what some of the things were I needed to play with to get what I want from his method.
I start with a basic two-tone mask that I crudely draw to give the model a main direction for the things I describe, then add a noise layer on top of it. From there it moves on to the first pass which takes an overly (#ollama) complicated series of concatenated input prompts and gives me a very rough (1024²) idea of where I'm headed. Then I crop a 16:9 section from that and scale it up a bit; this is also where the most of the color tweaking is done. Once I'm happy with this ""starting point"", I pass it on to another run through a different set of models to get my final image. Once I adjust the lighting on that one, it get's upscaled again for use as merely a wallpaper, maybe I'll print em out one day ...maybe.
Finally, today I've gotten my image composition layout to work the way I want, so I figure I'd share a few samples (1/4 scale).
Silly as it may sound, you'll almost always get best results by photographing the print in raw on a camera you trust. If you must scan them on a flatbed though, I'd recommend using the tried-n-true #xsane, as it gives you the ability to adjust the image during scan/preview in far greater detail than many other scanner programs. It also gives you the option to use ICM/ICC Profiles.
Fantastic! By far, the best style of video you've ever put out. I love reviews of stuff that offer advice in the way of; "here's a thing, a really good thing, but it might not be what you need/want". People need to use what works for their needs. But at the same time, you'll never know if something may be better for you unless you go play with it.
I've played around with almost every window management concept available for the past 20 years, they all have their place. In doing so, I've found that tiling in general is redundant to proper exploitation of virtual desktop capabilities, and hotkey configuration. For example, in #e16, I have multiple "desks", which are separate virtual desktops, and a 2x3 set of "areas" in each one which act more like what are commonly known as "virtual desktops". When I open a new program, I first place it on the desk and area I want it, then open a wm dialog for that window which allows me to select what I want the wm to remember for that program, such as location/size/border/opacity/etc. Now,
... Show more...
Fantastic! By far, the best style of video you've ever put out. I love reviews of stuff that offer advice in the way of; "here's a thing, a really good thing, but it might not be what you need/want". People need to use what works for their needs. But at the same time, you'll never know if something may be better for you unless you go play with it.
I've played around with almost every window management concept available for the past 20 years, they all have their place. In doing so, I've found that tiling in general is redundant to proper exploitation of virtual desktop capabilities, and hotkey configuration. For example, in #e16, I have multiple "desks", which are separate virtual desktops, and a 2x3 set of "areas" in each one which act more like what are commonly known as "virtual desktops". When I open a new program, I first place it on the desk and area I want it, then open a wm dialog for that window which allows me to select what I want the wm to remember for that program, such as location/size/border/opacity/etc. Now, every time I open that program, the wm places its window where I told it to remember. I've also set a few hotkeys for throwing windows to an adjacent area, or the same area on an adjacent desk, and ones for maximizing (full/horizontal/vertical) using only the available space. Using these methods gives me all the benefit I want from a tiling window manager combined with features of one that doesn't, all packed into a very small resource footprint.
And the bit where you mention grabbing and moving/resizing windows with mouse+key is one I would say is a tough contender with highlight-middleClick for the spot of best feature in any gui environment.
We do have rather decent robot wheelchairs, and the fully automated baggage check is outstanding. Not all the public service robots here are as rood as the floor sweeper ones. 😆
I wouldn't consider #e16 a DE (still count?); but using that, I prefer having a frame-only window decoration. I use a simple #xdotool line in my #conkyrc to display the currently focused window.
${exec 'xdotool getactivewindow getwindowname'}
I've also used a combination of xdotool, randr, and eesh in the past to do tiling and arrangement.
This is quite a common theme when you hear talk of #linux window managers. It seems to always be the same list of the same few, most of which are far less "easy" than advertised. Rarely do you see a mention of any #blackbox clone, and my favorite, e16, never even makes the long list.
I suspect it never makes the cut for #windowmanager reviews because of its lack of focus on #tiling. However, I believe #e16 is easily a formidable condender. It comes with very simple to read and configure keybind, menu, and window matching systems. The keybinds are in a single flat file, as are the menus which can also be called by filename for submenus. Because of the simplicity of just passing an executable, keybinds and menu items can do anything that can be done via command from a terminal. Unlike nearly all of the popular #WM flavours out there, e16 comes equipped with its own compositor, systray, and background manager. Best of all, its completely functional upon install without any preconfiguration needed.
@bazkie bumpercar, this here is the only post in which I have tagged you. I explicitly tagged the person (Uilebheist) to who's comment I was replying, not you. Their post on which I was commenting was pulled into my feed because @Randy Resnick, with whom I am friends, had previously commented on it. However, because the post to which I replied, was itself a reply to a post of yours, you were automatically tagged as a result, not be me as you can see from the attached screenshot of that post on my end. Uilebheist's claim of problems with their Mastodon experience is why I offered the advise of what resolved my issues with it and other fediverse interfaces. This is the reason I specifically addressed my comment to them, not you, nor anyone else. I apologize for inadvertently fouling your experience with the fediverse, it was in no way my intention. m(__)m
