![]() ![]() That's just one thing you can't customize. I can't get it - unless I resize my window to overlap to both sides of the screen, which is, well, silly. See that ridiculous, column-sized empty space to the right? There's actually another column just past it. This is with TweetDeck in fullscreen on my laptop at 1280 x 800 - a pretty popular resolution setting for 13" laptops. You might say, "hmm, so what, you can't resize, what's the big deal?" But the inability to resize columns (or for TweetDeck to even intelligently determine what kind of screen it's on and size columns accordingly), leads to foolishness like what's in this screenshot: ![]() In TweetDeck 1.3, you still can't resize columns, either individually, all at once, or dynamically, like in TweetDeck before version 1.0. ![]() Let's start with the bottom and work our way up. For the most part, the deficiencies, for me, come down to three long-established beefs I have with TweetDeck: It still uses web tech rather than OS-native application frameworks, it's not very customizable, and it offers a suboptimal experience on smaller screens - like, say, laptops. Now, not everything in the new TweetDeck is perfect. As far as I can tell, version 1.3 is a purely additive release nobody is going to be angry at a beloved-if-little-used-feature that's vanished. TweetDeck also keeps the features that have made it beloved by power users for years: scheduled tweets, scheduled accounts, syncing between clients across machines, etc. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |