» | 30 guest@cc 2020-03-21T00:31:35I don't particularly know the best way to format this post, so I guess I'll just type my thoughts as they come to me, just so I don't have to keep looking at this page knowing I haven't really contributed my fair share lol >>9 This post singlehandedly got me into fvwm a while ago. I love digging through old stuff to try to dig up cool dotfiles and stuff from long forgotten times. I've been waiting for an optimal point to post my desktop and I think I've gotten it to be good? maybe. >>28 I was like that when I was using herbstluftwm and bspwm. Having no bar and being fully enveloped into your working enviroment can be pretty nice, but sometimes windows are quite useful. I've made it to where I still have all of the functionality of bspwm and more, FVWM is extremely configurable, I also have a button to turn off decorations and panels so that it's basically back to being bspwm. >>29 >Also, I've always pronounced FVWM as "'Ehv-whem", and no one can stop me. Oh my, how devilish. Also, apparently i can't post with a pic for whatever reason, so that's a bummer. |
|
» | 42 guest@cc 2020-04-27T06:20:19>>38,16,15,14,13,12,11,10 also, these are all very cool and good desktops >>40 >I tend to like tiling windowmanagers more as they can switch between floating and tiling. not OP, but I used to use tiling managers and I just realized I'm fine with using the mouse. I appreciate the ability for efficiency with tiling managers, but dragging around windows is fine by me. Fvwm with some keybinds for keyboard only use is good for me. I don't need everything to be tiling all the time. |
|
» | 58 guest@cc 2020-08-27T13:17:31 [ImgOps] [iqdb]File: 60ebaab9f386df151dbc77ea41b2a5… (PNG, 539.8KB, 670x900) | >>57 normally i should've stopped reading at that _lowercase_ letter p, but i chose to give it a look >Non-square pixels can be represented (see the pHYs chunk), but viewers are not required to account for them; a viewer can present any PNG file as though its pixels are square. not only it has "are not required" wording, but also it explicitly says a viewer can perfectly ignore it (which an image viewer should do if it sees that "nonsensical" value) compared to their comment on other ancillary chunks with "should" and "need": >To produce correct tone reproduction, a good image display program should take into account the gammas of the image file and the display device >Viewers that have a specific background against which to present the image (such as Web browsers) should ignore the bKGD chunk, in effect overriding bKGD with their preferred background color or background image >If the image has a tRNS chunk, the viewer will need to adapt the suggested palette for use with its desired background color >For images of color type 6 (truecolor with alpha channel), any suggested palette should have been designed for display of the image against a uniform background of the color specified by bKGD. >If practical, decoders should have a way to display to the user all tEXt and zTXt chunks found in the file other than these, most of others are "can", and a small amount are "are not required", but none of them explicitly suggests ignore
>And your anime girls are terribad. according to what you posted? wrong
|
|
» | 65 guest@cc 2020-08-30T13:38:04 [ImgOps] [iqdb]File: ratio.PNG (PNG, 1.2MB, 872x989) | >>64 >Wrong way around saying to yourself? pic related: all videos here have 16:9 aspect ratio, but the one opened contains "Original display aspect ratio" which says 3:2 (other videos don't have this) the windows thumbnailer respects this ratio, rescales it to 3:2, and cuts off edges so that it fits into 4:3, just like a tv does; mpv does not as a result, they display that video in different aspect ratios, while for other files they display the same just tell me which one is displayed properly on a pc, as intended by the author, as opposed to catering to tv limitations?
|
|