We're continuing to update Version 5 with all back-ported bug fixes, and just released a new major update to it last month. So, I'm not sure I follow. We encourage you to find something that works for you if ours does not, but of course are always hoping to do a good job such that you're feeling our software is worth $10 per 12 months of usage, so that we can continue to reliably fund development. This issue is a complex topic, with a complex solution. It might not seem like i
Dr W - Fences Support
Hi cnw_uk, good news, if you're not seeing it, it should be on as it is now on by default. If you continue seeing the problem with the new version available v6.52, let us know and we'd like to gather more debug data from you to try to help us see the problem, but hopefully this resolves it. Thanks for the help in return
For sure! If it's all patched up for you, feel free to purchase an additional license down the line for your use or for sharing and glad we could help.
Hi dod, thanks for bringing this up. Indeed- it was a scant used feature (and a destructive one at that), and so it was removed some years ago. The team is always open to hearing about new use cases however. At minimum, an idea that comes to mind might be "shift + click" reveals this option, might be a possibility to bring this back. (Unintuitive, but, perhaps you might have found it?) In particular – we'd love to hear more about you usage, if you'd have the patience to
Got it! Noted for team thank you!
Hi, not sure what is meant here, could you share more?
Yup there is a bit of a natural upper limit to the corner radius. If it exceeds the size of half of the size of the titlebar, you'll start to see visual fragments when it is rolled up, or in tabs, etc. @helios.kc sounds good. Feel free to share a screenshot so that we can see how it ended up! Cheers.
Hi coprof, Could you check to see if these directories exist on your system? %appdata%\Stardock %appdata%\Stardock\Fences If not, could you try creating and seeing if the issue is resolved? If so, we'll have to see about putting additional checks to ensure it exists at this point, as it should have been created by then. Thanks for the help
Hi Ken, this is a known issue that has come about, that we believe we've gotten resolved. Please refer to the latest beta, which you can download here: Fences6_6.5.2.7-j136-Setup.exe Let us know if this helps, thanks!
Link to the beta is at Fences6_6.5.2.7-j136-Setup.exe Thanks!
Hi Crash28 and others. Per previous posts, we believe we've gotten a handle on this issue. We'll be porting the fix to Fences 5 as well, but the beta link for this in Fences 6 is here: Fences6_6.5.2.7-j136-Setup.exe Hopefully this takes care of it, but if not, continuing to hope for latest debug logs. Thanks</
Hi Daishi, Per posts here, the new beta version is available that should resolve this. Please let us know if this takes care of it. Thank you! Link is here: Fences6_6.5.2.7-j136-Setup.exe
Hi Daishi! This is a bug actually! We have a fix coming out for that this week. Under certain scenarios, it was possible to click UNDER a Fence like this. This is fixed and we should be able to share a build here on the forums likely tomorrow.
Always looking to make the app better! Yup yup, applies to grid as well, which is a problem subset of auto-arrange at a technical implementation level, but yes ideally we find a place for it in the UI itself in plain english. Will do!
Hi lalaland121, yes I'll second, in asking what setting you'd like to adjust? As basj writes, the default behavior is now that it will remember your layout on a per-configuration basis, without any need to adjust settings manually.
Hi Roy thanks again for the suggestion. This has been added for the next version, upcoming, v6.53, which is likely hitting beta later this week. If you've already been refunded, happy to share a link here so that you can give it a try. It's not in the UI, but settings for the option is at: HKEY_CURRENT_USER\Software\Stardock\Fences\Settings (DWORD) AllowAutoArrangeUnderDockedGroups = 1 0 = current default, 1 ignores groups docked to top during auto-arrange, 2 ignores
Hi Roy, this is the current intended functionality, but we'd be glad to look more into more fine tuning this algorithm. As is, we improved the algo for making sure icons didn't get covered up, which was a common support problem, but some of it may have gone too far. Could you share more about whether you have auto-arrange on, grid on, etc? Looks like you're hoping for specifically: "docked to edge" rolled up groups would not block out icons? Wondering if you're thinking non-docked-to-
Hi Rooj, seeing if this is still occurring? If so please see post above?
Got it! Always happy to learn more about what folks are putting on their desktop, as to work well alongside. Feel free to share the screenshot or name of the widget and we can take a look. We're looking as well at giving some additional background blur and Windows-matching styling options in a future version too, in even those might match some of the stylings of your widget app. Thanks for the context
@ Crash28, we're feeling pretty sure your issue falls into the bucket of an outstanding issue we were seeing with "Large" icons, so, this should be addressed for the next release. Windows was reporting incorrect values to us for Large and better, and we hadn't found a proper source for spacing reading that also was reliable with mid-session changes to DPI. @ iotivedo, this may addre
Hi helios, Yes, there is an undocumented switch at "FencesBackgroundCornerRadius". You can set this at HKEY_CURRENT_USER\Software\Stardock\Fences\Settings (DWORD) FencesBackgroundCornerRadius = 4 Press F5 and it should refresh, though and explorer restart may be necessary. We've noticed that the background blur does not seem to obey changed values given it's undocumented state, so we've made note to get that fixed for the next release. Any
A couple pieces here to note: - Unless we're missing it, not seeing any debug log upload. - @rick_summon, recounting, the issue seen is that icons within fence groups get scrunched up sometimes when returning from sleep. Othertimes, it is normal. "Use same spacing" is off, but toggling it on and off seems to resolve. It's unsaid whether the issue happens for the loose desktop icons or only within Fence groups - @crash28, from your posts so far, it you do have "Use
Hi all – just to update status on this, we're going to be revisiting this here. Some context on what makes this a hard problem: - Explorer effectively lies about spacing. When querying, there are many scenarios in which it gives incorrect metrics, so, it needs to be inferred. Basically any change ever of DPI during a session, in particular, makes things whacky, even when returning to the base DPI. This can include simply monitors going to sleep, which under the covers often "c
Hi. <p class="p1" style="margin: 0px 0px 12px; font-style: normal; font-variant: normal; font-size-adjust: non
Hi. <p class="p1" style="margin: 0px 0px 12px; font-style: normal; font-variant: normal; font-size-adjust: non