Recommended Posts

Soapy give it a try! For those who haven't Tabs on Top, I think certainly is better!...

But the fact is that you need for sure light-backgrounds... Not a problem for me, cause I use anyway light backgrounds.

Soappy... Bro, just a suggestion... I thought you will exclude Nav-Bar! Lost it's perfect color... My personal opinion is to leave the Nav-Bar with Solid color... Transparent only Personal and Tab bars when Tabs aren't on Top.

Also... When I hover on Addon Bar, the first button on the right, appears on the Scroll-bar... I don't know if you consider this as bug, but couldn't be a bit more left?

And something last... Could you give us an option if we want Tabs on Title bar or not? It could be nice feature in your userstyle page...

And something really last... Whichever button I place on Tab bar I would like to take the exact shape of "Open New Tab" button...

Well... These weren't just one suggestion!

Of course the choice is yours :p

Soappy... Bro, just a suggestion... I thought you will exclude Nav-Bar! Lost it's perfect color... My personal opinion is to leave the Nav-Bar with Solid color... Transparent only Personal and Tab bars when Tabs aren't on Top.

Also... When I hover on Addon Bar, the first button on the right, appears on the Scroll-bar... I don't know if you consider this as bug, but couldn't be a bit more left?

And something last... Could you give us an option if we want Tabs on Title bar or not? It could be nice feature in your userstyle page...

And something really last... Whichever button I place on Tab bar I would like to take the exact shape of "Open New Tab" button...

Well... These weren't just one suggestion!

Of course the choice is yours :p

I have no clue how to use the userstyles.org settings :blush: Or I would make almost everything an option. If you don't want Tabs in titlebar I have it commented near the bottom of the code and you can remove it.

My main priority was to make tabs on bottom actually work and look decent, I'll see what people think about it and make changes if needed. Again if I can figure out the settings I'll add an option to make buttons like tabs in the TabsToolbar.

I know that I can remove the proper code... But I'm just saying that could be better, generally! You know well that if you give options the user is happier!

Well, about buttons on tab-bar, if you make 'em exactly like "Open New Tab" ( shape, width etc ) could be perfect! But then we need Tabs NOT on Title bar, because we loose precious space. Especially If we willing to put buttons on Tab-bar.

What about the Add-on Bar? It touches the Scroll-bar and its function of "Down button"

Just suggestions, bro... I don't have any personal request.

P.S. I don't know either how to create options in userstyle.org. The Mentor foxxyn8 knows! If you meet him, ask him! He helps everyone! Along with Tabs on Title bar or Not, you could give us option for Solid Nav-Bar or Fully Transparent!

Hey Soapy, I tried to apply your style but got a little error.

y5d.png

Have you got it before? Is there a fix already?

I tried to edit your code to see if I could at least find where is the problem, but didn't find much, sorry =X

If it is just with me, maybe it is the Personas that caused it...

Besides that, your style looks amazing, good job o/

Hey Soapy, I tried to apply your style but got a little error.

Have you got it before? Is there a fix already?

I tried to edit your code to see if I could at least find where is the problem, but didn't find much, sorry =X

If it is just with me, maybe it is the Personas that caused it...

Besides that, your style looks amazing, good job o/

Looks to be personas or maybe another userstyle you have enabled? I need to add support for personas..

I'm currently working together with SoapyHamHocks on his Firefox 4 Windows 7 style and just wanted to give you an impression of what our In-Content UI could look like, if we manage that everything opens in a new tab instead of a Pop-up.

http://dl.dropbox.com/u/4681041/in-content.jpg

Since I've installed beta 7, when I click on the firefox menu button, the button turns transparent. I think that it may have to do with the stylish code I posted below. I'm not sure what I need to change to fix the problem though. Anyone know how to fix it?

#appmenu-button .button-text
{ 
    color: transparent !important;
    text-shadow: none !important;
    margin-left: -27px !important;
    margin-right: -33px !important;
    background: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAADK0lEQVQ4jV2TTWxUZRSGn++7d+bey3SYMgMzdNLMTCu2VcE0CjG1qYqRSEhYKElTA66MooaNLozDwh8WjAs3JsSFSxeKRg0axSj+EApFYotAS0ctWmeEOpTS6fx0fu+9n4v+pPqsTk7yvuck57wCIGXIT4BUsu6OBbr2bO+p5J71OfWHxvzxMEuMA6eBLwu/nxxlDWLZQAGcDG09Ou/xDR3IXegE2F9zEMDg/rd59eky1z467575pfLdrrmLRw7dqJxjWXwgZUh1682gShlSra2Ha0qdK9nq63xDbXniLTUx8pz68Y1+9U5XuPrhwMZBACkEjwRDGgD7hoLE457V9c4GNF5u9XK1WGfw4B4efT1B594eHnvlHrNUku99/mRks9SkuL/jTk+jkrVxF6ps7/Ovmu0bChKXUEQnH9uCMrx8MNJK4sEIoZgVKN9sJqXHENFou+ZtVl18iaXp1UKEjbuf4dPj86hTC1y+eJuJM3/hojF5rUGhYNO9K8TiXG2nrhTrfa0SXQoqJUnLwB0A6J5JAGamcuQn05RmctiuzlhaYkmHSNxkMe/06PWaa2CD2SYZ/rZE8/tRZnIKgKOPv0vz/Y8RysGSLtWaIJKo0Lp+nnylQq1o69LwiHKpoEBAMKKxye/S1iYBOPzNi3zW9wOv7chQnJ2jUczzcHsW8vOUf72J1SIqugZX/sk2+/0bNLruNvl73GZbXOfeHSY+0+ZC5hacOI3d/jwxK8vB3jT1XIPrZ/Nowh3XbUcdnxpv3BcI6VY4ZtK+LYjdcBj7aZHMHw3gKknfU/Sv+40Xdt8mpNVZmFpg8mcNb2vwlEgZssXSGNaF6N055Mc0dBxHR5oa03kvc8Ua68QisXCTRMKgik56pMyfGau4ObapWwAcMeQDluQLS4rw1j6LSFRD1ySapjCkjeMIbMAMQSarmLhUr81NOwPJujsqVr4uZcheQ+MrBdFQi6Sz20sgKNAtwCOYvd4kc0OgqnYlN+v2J+vupdUwrXDMp3W4gpdcpfY6UiQce+k6piHYEJA1p6lOlBfU4UOLzvR/0vh/jvm0DuAuILrcmgHSa4Ur/AsXclHwqDchzQAAAABJRU5ErkJggg==") no-repeat 16px !important; }

Here's a screenshot showing what I'm referring to:

1zzmhip.png

Since I've installed beta 7, when I click on the firefox menu button, the button turns transparent. I think that it may have to do with the stylish code I posted below. I'm not sure what I need to change to fix the problem though. Anyone know how to fix it?

Do you have something like this in your script:

#appmenu-button:hover:active, #appmenu-button[open] 
{
    background-image: -moz-linear-gradient(rgba(0,0,0,.2), rgba(0,0,0,.1) 10%, transparent 60%), -moz-radial-gradient(14px, circle cover, rgba(248, 233, 164, 0.5) 29%, rgba(248, 233, 164, 0.2) 35%, rgba(248, 233, 164, 0) 50%) !important;
    -moz-box-shadow: 0 0 4px rgba(0,0,0,.4) inset !important;
}

If so just adjust the rgba values of the background image gradient OR just set a solid background.

Example:

#appmenu-button:hover:active, 
#appmenu-button[open] {
    background-image: -moz-linear-gradient(rgba(255,0,0,.5), rgba(255,0,0,.4)), -moz-radial-gradient(14px, circle cover, rgba(255, 233, 164, 0.5) 29%, rgba(248, 233, 164, 0.2) 35%, rgba(248, 233, 164, 0) 50%) !important;
    -moz-box-shadow: 0 0 4px rgba(0,0,0,.4) inset !important;
    border-radius: 0 0 5px 5px !important;
}

post-350326-12891727125084.jpg

Ok I found this in my code:

#appmenu-button:hover:active, #appmenu-button[open]
{    background-image: -moz-linear-gradient(rgba(0,0,0,.2), rgba(0,0,0,.1) 10%, transparent 60%), -moz-radial-gradient(14px, circle cover, rgba(248, 233, 164, 0.5) 29%, rgba(248, 233, 164, 0.2) 35%, rgba(248, 233, 164, 0) 50%) !important;  }

Which part do I need to change in order to make the button orange when clicked, instead of transparent, like it currently is?

Ok I found this in my code:

#appmenu-button:hover:active, #appmenu-button[open]
{    background-image: -moz-linear-gradient(rgba(0,0,0,.2), rgba(0,0,0,.1) 10%, transparent 60%), -moz-radial-gradient(14px, circle cover, rgba(248, 233, 164, 0.5) 29%, rgba(248, 233, 164, 0.2) 35%, rgba(248, 233, 164, 0) 50%) !important;  }

Which part do I need to change in order to make the button orange when clicked, instead of transparent, like it currently is?

if you just want it solid orange replace

background-image: -moz-linear-gradient(rgba(0,0,0,.2), rgba(0,0,0,.1) 10%, transparent 60%), -moz-radial-gradient(14px, circle cover, rgba(248, 233, 164, 0.5) 29%, rgba(248, 233, 164, 0.2) 35%, rgba(248, 233, 164, 0) 50%) !important;  }

with

background: orange !important;

If you want to keep the gradients then look at the example I gave in my previous post, which turned the appmenu button red.

What is the rgba code for orange? I want to keep the button looking the same. The only thing I want to change is the background color to orange.

The rgb value for orange is (255,165,0). The "a" is the alpha value which determines the level of transparency. Values are from 0 - 1 with 1 being fully opaque and 0 being fully transparent.

The rgb value for orange is (255,165,0). The "a" is the alpha value which determines the level of transparency. Values are from 0 - 1 with 1 being fully opaque and 0 being fully transparent.

This is the current code I have:

#appmenu-button:hover:active, #appmenu-button[open]
{    background-image: -moz-linear-gradient(rgba(0,0,0,.2), rgba(0,0,0,.1) 10%, transparent 60%), -moz-radial-gradient(14px, circle cover, rgba(248, 233, 164, 0.5) 29%, rgba(248, 233, 164, 0.2) 35%, rgba(248, 233, 164, 0) 50%) !important;  }

which part of the code do I edit in order to change the background color to orange, when the button is clicked? I've tried changing the numbers that are in the rgba parentheses, but I just get errors.

This is the current code I have:

#appmenu-button:hover:active, #appmenu-button[open]
{    background-image: -moz-linear-gradient(rgba(0,0,0,.2), rgba(0,0,0,.1) 10%, transparent 60%), -moz-radial-gradient(14px, circle cover, rgba(248, 233, 164, 0.5) 29%, rgba(248, 233, 164, 0.2) 35%, rgba(248, 233, 164, 0) 50%) !important;  }

which part of the code do I edit in order to change the background color to orange, when the button is clicked? I've tried changing the numbers that are in the rgba parentheses, but I just get errors.

Just use this:

#appmenu-button:hover:active, 
#appmenu-button[open] {
    background-image: -moz-linear-gradient(rgba(255,165,0,.8), rgba(255,165,0,1)), -moz-radial-gradient(14px, circle cover, rgba(248, 233, 164, 0.5) 29%, rgba(248, 233, 164, 0.2) 35%, rgba(248, 233, 164, 0) 50%) !important;
    -moz-box-shadow: 0 0 4px rgba(0,0,0,.4) inset !important;
    border-radius: 0 0 5px 5px !important;
}

post-350326-12891968061098.jpg

Since I've installed beta 7, when I click on the firefox menu button, the button turns transparent. I think that it may have to do with the stylish code I posted below. I'm not sure what I need to change to fix the problem though. Anyone know how to fix it?

They are finally getting around to releasing it? It's so far behind beta8pre now that I shudder to think about using it.

Just use this:

#appmenu-button:hover:active, 
#appmenu-button[open] {
    background-image: -moz-linear-gradient(rgba(255,165,0,.8), rgba(255,165,0,1)), -moz-radial-gradient(14px, circle cover, rgba(248, 233, 164, 0.5) 29%, rgba(248, 233, 164, 0.2) 35%, rgba(248, 233, 164, 0) 50%) !important;
    -moz-box-shadow: 0 0 4px rgba(0,0,0,.4) inset !important;
    border-radius: 0 0 5px 5px !important;
}

Thanks. That works perfectly. So is it supposed to be transparent when you click on the firefox button, or is it a known bug?

Can anyone help me to understand why I can't install Stylish on the latest build of Minefield...?

I have done the about:config - extensions.checkCompatibility.4.0b and set it to False. This is saved and then restarted but I get the warning and refusal to allow Stylish to install and I assumed that entering what I have done would disable the compatibility check..? This has worked for me on the previous beta builds of FF 4.

Thanks

Just use this extension to disable compat check: Add-on Compatibility Reporter

Looks to be personas or maybe another userstyle you have enabled? I need to add support for personas..

Not really, when I was testing yours I removed all the other scripts I have. Now I'm currently using a custom one that is like pieces of scripts I got and a bit of mine as well... But I must say yours look better, the only point I really mind is the Minefield Button, which I can easily edit on most scripts.

It happens with any script if it has Tabs on Title bar. Probably needs extra support.

Soapy you've to give attention to something else too... At your AppMenu button, when FF losing focus, the Blue button remains blue. But when you're in Private Mode, the Purple button becomes Transparent... Shouldn't behave both with the same way?

Foxxyn, bro, how I can move 1 px all bars closer to App menu button? ( Tabs not in Title bar )

It happens with any script if it has Tabs on Title bar. Probably needs extra support.

Soapy you've to give attention to something else too... At your AppMenu button, when FF losing focus, the Blue button remains blue. But when you're in Private Mode, the Purple button becomes Transparent... Shouldn't behave both with the same way?

Foxxyn, bro, how I can move 1 px all bars closer to App menu button? ( Tabs not in Title bar )

The current value in my skin is -8 so try -9.

#main-window[chromemargin^="0,"][sizemode="normal"]:not([inFullscreen="true"]) #navigator-toolbox {
 margin-top: -9px !important;
}

I'm trying to build a code that can adjust every button about #toolbar buttons -except the #back button... But it doesn't working well...

Can you please fix it for me? With the normal numbers... Padding, Border-radius etc... Something like this:

#nav-bar toolbarbutton:not([#back-button]){
    margin: 5px !important;
    border-radius: 1px !important;
    padding: 0 8px !important;
    box-shadow: none !important;
    min-height: 22px !important;
}

Soapy, the update is coming?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • AMD RX 9070 GRE AI, Blender benchmarks vs 9070 XT, 7800XT, Nvidia RTX 5070, 4070 by Sayan Sen Earlier this week, we shared the first part of our review of AMD's new RX 9070 GRE. It was about the gaming performance of the GPU, and we gave it an 8 out of 10. As a follow-up, similar to how we did with the 9070 XT and non-XT, we are doing a dedicated productivity review for the RX 9070 GRE as well, where we compare it against the 9070 XT, 9070, 7800 XT, as well as Nvidia's 5070 and 4070. This will include AI, rendering, compute, and more benchmarks. AI performance, especially, is a very important metric in today's world, and AMD also promised big improvements thanks to its underlying architectural improvements. We will be pitching it against the data we already have for the RX 9070, and RX 9070 XT, but also the Nvidia 5070 FE, MSI GeForce RTX 4070 VENTUS 2X 12G, and Gigabyte Radeon RX 7800 XT GAMING OC 16G as they are in a similar price class, but also because we do not have a comparable 5060 Ti card lying around here that we can compare it against. Before we get underway, this is a collaboration between Sayan Sen and Steven Parker, who lent me his test bed. Also, there was no editorial input from AMD. First up, the specs of the RX 9070, 9070 XT, and 9070 GRE, which were given to us by AMD: Radeon RX 9070 GRE Radeon RX 9070 Radeon RX 9070 XT Boost Clock: Game Clock: up to 2.79GHz up to 2.20GHz up to 2.52GHz up to 2.07GHz up to 2.97GHz up to 2.40GHz Stream Processors 3,072 (48 CU) 3,584 (56 CU) 4,096 (64 CU) Ray Accelerator 48 56 64 AI Accelerator 96 112 128 ROPs 96 128 Texture Mapping Units 192 224 256 Memory 12 GB GDDR6, 18Gbps Clock, 192-bit Bus 432 GB/s 16 GB GDDR6, 20Gbps Clock, 256-bit Bus Effective Memory Bandwidth: 640 GB/s Infinity Cache 48 MB (3rd Gen) 64 MB (3rd Gen) Card Bus PCI-E 5.0 X16 Output 2x HDMI 2.1b 2x DisplayPort 2.1a Power consumption 220W 304W Recommended PSU 650W 750W Slot width 2x 3x Price (SEP) $549 $599 As you can see from the specs above, it is less than the standard RX 9070 in every way that counts, except for slightly higher Boost and Game clock speed. Design Moving on, the RX 9070 GRE we were given is an XFX Swift triple-fan, dual-slot design with two 8-pin connectors. At 30cm (self-measured), it will fit in most systems easily. There is no RGB either. The AMD Radeon RX 9070 GRE by XFX from all angles. Test system Our test system consists of the following: Lian Li O11 Dynamic Mini V2 Flow (Amazon|Newegg) ASUS Z890 ProArt Creator WiFi (Amazon|Newegg) Intel Core Ultra 7 270K Plus (Amazon|Newegg) Thermal Grizzly KryoSheet - 44x37 (Amazon|Newegg) 2x 16GB G.Skill Trident Z5 RGB (7200 MT/s in XMP) (Amazon|Newegg) Sabrent Rocket4 Plus 2TB SSD (Amazon) Windows 11 25H2 (Build 26200.8246) AMD shared a press driver based on the recently released Adrenaline 26.5.2 that we were required to use. We now move on to our benchmarks. First up, we have Geekbench AI running on ONNX. For some reason, the 9070 GRE does exceptionally well here in both half-precision (FP16) and single-precision (FP32). It manages to beat the RTX 5070 and RX 9070 non-XT, and is only behind the 9070 XT. Since Geekbench runs in short bursts instead of continuously hammering the graphics card, it seems the GRE's faster boost clocks are helping here. Next up, we move to the UL Procyon AI test suite, starting with the image generation benchmark. We chose the Stable Diffusion XL FP16 test since it is the most intense workload available on Procyon. The Nvidia cards do very well here, as even the 4070 out-muscles AMD's best fairy easily. The positive thing about the GRE is that it gets quite close to the 9070 non-XT in this test; this indicates that the VRAM does not play a very big role here, as SD XL relies on float16 (FP16). So this is something to keep in mind again. If you wish to work with float32 AI workloads, graphics cards with larger than 12 GB buffers would likely emerge as victors. Regardless, the gains are still massive on AMD's 9000 series compared to the 7000 series. Following image generation, we move to the text generation benchmark. This is one test where the 9070 GRE struggled, quite a lot. It seems that the 12 GB VRAM and lower memory bandwidth of the new Radeon 9070 GRE are hurting it quite a bit; the split is massive, especially in a test like Llama2, which packs 13 billion parameters. As such, in all the tests, the 9070 GRE is the slowest of the lot. Next, we tried Blender, and here the AMD GPUs were beaten by Nvidia. Rendering is something the Green team has always had a lead over the Red side, and it has not changed so far. On the positive side, though, the 9070 GRE shows significantly better results than the 7800 XT, which means AMD is on the right path. Catching up to Nvidia, though, will require a lot more effort. And we hope HIP and ROCm can keep improving. Wrapping up AI testing, we measured OpenCL throughput in the Geekbench compute benchmark. The RX 9070 GRE alongside the 9070 did not fare well here at all, even falling behind the 7800 XT. Interestingly, even the RTX 5070 could not beat the 4070 on OpenCL, so perhaps this suggests that OpenCL optimization may not have been a priority for either AMD or Nvidia in the modern era. Conclusion We reached the end of our productivity performance review of the 9070 GRE, and we have to say it's a mixed bag. Unlike the 9070 and 9070 XT, the GRE excels in some areas while losing ground fairly easily in others. Similar to how it happened in gaming, any time the card's memory subsystem gets hammered, it tends to fall behind the others. This was the case with text generation, wherein we saw the VRAM sometimes hit its maximum available 12 GB of usage with larger model sizes. So what do we make of the RX 9070 as a productivity hardware? It can certainly be used, but you have to know it has its limitations. For those looking for a GPU that can deal with more, AMD recently unveiled the Radeon AI PRO R9700, which is essentially a 32 GB refresh of the 9070 XT with some additional workstation-based optimizations. On a similar note, the new Ryzen AI Halo platform is something you can consider if you want to set up a local AI processing station. Considering everything, we rate AMD's Radeon RX 9070 GRE a 7.5 out of 10 for its productivity performance. Price is less of a factor for those looking at productivity cases compared to those considering the GPU for gaming, and as such, we felt it did quite decently on many occasions and can be handy if you need a 12 GB GPU and, for some reason, don't want to get Nvidia. Purchase links: RX 9070 / XT / GRE (Amazon US) As an Amazon Associate, we earn from qualifying purchases.
    • Does anyone here know if these updates are integrated into the UUP dump isos?
    • Motrix Next 3.9.4 by Razvan Serea Motrix Next is a modern, open-source cross-platform download manager built as the official next-generation successor to the original Motrix project. It has been completely rewritten using Tauri 2, Vue 3, TypeScript, and Rust, while still relying on the powerful Aria2 download engine for high-speed multi-protocol transfers. The app supports HTTP, HTTPS, FTP, BitTorrent, ED2K and magnet links, offering advanced features like multi-connection acceleration, task scheduling, bandwidth control, and batch download management. With a significantly reduced install size (around 20MB), it focuses on being lightweight, fast, and resource-efficient compared to traditional Electron-based download tools. Designed for Windows, macOS, and Linux, Motrix Next delivers a clean, modern UI inspired by Material Design 3 principles, with smooth animations and a minimal workflow. It improves usability through better download organization, system tray integration, and enhanced torrent handling including selective file downloads and tracker management. Motrix Next features: Multi-protocol downloads — HTTP, FTP, BitTorrent, Magnet, .torrent, ED2K, and Metalink tasks BitTorrent — Selective file download, DHT, peer exchange, encryption controls, metadata caching, GeoIP peer flags, and tracker probing Browser extension integration — Embedded Extension API with independent authentication, download confirmation, smart auto-submit, filename hints, referer/cookie forwarding, and real-time controls (Chrome Web Store · Edge Add-ons) Safe filename handling — Content-Disposition, RFC 2047, non-UTF-8, percent-encoded, and extensionless URL resolution with path traversal sanitization Download organization — Favorite and recent folders, optional file-type categorization, stale-record cleanup, and completed history backed by SQLite Concurrent downloads — Independent controls for active tasks, HTTP connections per server, segments per file, and BT peer limits Speed control — Global and per-task upload/download limits with day-of-week and time-of-day scheduling System integration — Tray operation, optional tray speed display, macOS Dock badge/progress, protocol handlers for magnet://, thunder://, and motrixnext:// Lightweight mode — Destroys the WebView on minimize-to-tray while Rust keeps the engine, task monitor, notifications, history, and extension routing alive Notifications and power options — Native task start/complete/failure notifications, keep-awake during downloads, and optional shutdown after completion Network controls — Scoped proxy support for downloads, app updates, and tracker updates, plus system proxy detection Auto-update channels — Stable, Beta, and Latest Across Channels policies with separate download and install phases Diagnostics — Structured logs, exportable diagnostic ZIPs, database integrity checks, automatic DB rebuild, and Linux GPU rendering fallback Personalization — Light/dark/system theme, 10 color schemes, 26 languages, and first-launch system language detection Motrix Next 3.9.4 changelog: Motrix Next 3.9.4 promotes the 3.9.4 beta cycle to stable. This release refreshes bundled engine binaries, improves task detail readability and copy actions, expands link handling for magnet and ED2K workflows, polishes responsive navigation and text wrapping, updates browser extension documentation, and refines network preference controls. New Features Task Detail copy actions — Added copyable values for task metadata and reusable render functions for long text fields. Magnet and ED2K lifecycle support — Added task lifecycle handling for magnet and ED2K links. History cleanup for deleted tasks — Deleted tasks can now remove matching history records. User-Agent management — Added user-agent management and improved related network preference controls. Browser extension documentation — Added the Firefox Add-ons link for the Motrix Next extension. Improvements Engine binaries — Updated bundled binaries for supported architectures. Task Detail readability — Long task names, URLs, tracker values, and copyable metadata now render more clearly. Deletion messaging — Refined localized task deletion text for clarity and consistency. Text wrapping — Improved URI input wrapping and task name multiline display. Navigation layout — Improved sub-navigation responsiveness. Disk allocation default — Changed the default file allocation method to trunc. Proxy controls — Improved proxy button styling in network preferences. Download: Motrix Next 64-bit | ARM64 | macOS ~20.0 MB (Open Source) Links: Website | macOS / Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • NVIDIA officially supports Ubuntu, as linked above with the GeForce NOW Hands on I did in collaboration with Paul Hill.
    • TO be clear I am not running linux today, however I keep thinking about it. And I want to make sure there are minimal obstacles if I decide to make that switch in the coming months.
  • Recent Achievements

    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
    • Dedicated
      Mark Spruce earned a badge
      Dedicated
    • Collaborator
      conkir earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      479
    2. 2
      PsYcHoKiLLa
      250
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      FloatingFatMan
      67
  • Tell a friend

    Love Neowin? Tell a friend!