Curtains - Beta 3 issue report thread (Closed)

from Stardock Forums

With the beta 3 release of Stardock's newest app, Curtains, we are creating this thread so that members can report any observed issues.  

At this time, the Curtains beta is restricted to current Object Desktop members only.  

Obtaining the Curtains beta:

Object Desktop members can get the Curtains beta from within Object Desktop Manager with 'show beta downloads' enabled:

f

It can also be obtained from your Object Desktop account page:

https://store.stardock.com/myaccount/products

Reporting an issue:

Please include the following for anything found:

  • Exact Windows version \ build (winver.exe)
  • Detailed steps to recreate the issue seen
  • Screenshots and videos are very helpful.  Videos can be uploaded to a cloud drive services (GoogleDrive, DropBox, OneDrive, YouTube) and links included in your post.  Images can be directly added.
  • If there are specific apps that Curtains does not work (well) with, please note what apps and their exact versions.  If any app is not common, a link to a trial version would be appreciated.

Thank you all for your interest in Curtains and for helping us make it even better.

Sean Drohan
Stardock Support Manager

curtains support
26,731 views 18 replies
Reply #1 from Stardock Forums Top

Changelog for Beta 3

  • The online tab filters option now does not incorrectly switch to all if you click away from it
  • The online tab filter is now in bold to make it more obvious
  • The online tab list now shows the blurb on mouseover complete with animation
  • Animations on the online tab are now smoother
  • When text shows on mouseover, on the online items, it now caps it to an exact number of lines so you don't get part lines showing
  • If you download a style, apply it and then click edit, you previously had bits from the previous style being edited. This is now fixed.
  • List now shows a better mini preview
  • Online tab now shows fewer items but looks better
  • Fixed clear custom preview button not working
  • Should better reset your previous light/dark choices when switching between styles rather than sticking with the last values set by a style
  • Fixed an issue with tile sometimes losing the right/bottom borders
  • UI tweaked with some gradients in places
  • UI adds an option for applying styles to compatible Universal apps (UWP) but this is nonfunctional currently as noted in the UI
  • Advanced properties now lets you enter hex colors and fixes the missing more button on some colours
  • Scrollbars in-app now smoothly move and have a downstate to make them more obvious to use
  • Advanced editing page combo box now is limited in size to stop it showing above the combo box on some machines
  • Online tab now defaults to featured and sorts other categories by rating
Reply #2 from Stardock Forums Top

Known issues:

For any issues that are reported, and that can be reproduced \ verified, they will be listed as 'known issues' and itemized here.

  • There is not a system try icon for Curtains - this will be added in future versions.
  • While Curtains mentions Groupy - and has Groupy sections for styles - it will not apply to Groupy 1.32 .  A future update to Groupy will add support
  • UWP apps (Settings UI in Windows 10 for example) are not currently supported but we are investigating extending support to those in future betas.
  • If you also have Windowblinds installed, and when a Curtains skin is applied, the Start10 start button control by Windowblinds is not released. You can't go into Start10 and change the start button - one needs to go into Windowblinds and un-tick "Always use the OS start button rather than the style one". 
Ashes of the Singularity II
Reply #3 from Stardock Forums Top

With the release of Beta 3:

https://forums.stardock.com/500043

This thread is now closed. 

Thank you all for your feedback here - it is very much appreciated.

Sean Drohan
Stardock Support Manager

Reply #4 from WinCustomize Forums Top

I keep seeing dark text on dark backgrounds.

 

 

 

 

 

 

 

 

Reply #5 from Stardock Forums Top

Quoting RedneckDude, reply 4

I keep seeing dark text on dark backgrounds.

 



 

 

 

 

 



 

 

It looks like you are altering your system colours somehow which continue to be applied once curtains has been applied.

Please apply Windows 10 look in WB, ensure your colours are set normally (that's light grey for the background of that about box) and then apply curtains styles.

Reply #6 from WinCustomize Forums Top

Win10 v1909 build 18363.778

Ultimately a "nothing-burger" for me but I should mention it.  After installing this beta, the first time I applied a Curtains theme Explorer instantly went into a constant crash-reload loop, while the Curtains UI was still open, which I stopped by applying the Default theme once again.  After that, themes loaded fine.

Details: I primarily run on a Standard user.  Admin user runs on default Win10, no themes.  To install the beta, I applied the Default theme on the Standard user, logged out, logged into Admin.  Disabled anti-virus, deactivated Curtains, uninstalled prior beta checking first box ("Delete settings" or such) didn't check second box ("Apply Default theme" or such). Restarted.  Logged into Admin, disabled anti-virus, installed new beta .  Activated Curtains, closed UI, enabled anti-virus, Restarted.  Logged into Standard user and applied the Curtains theme.

Reply #7 from WinCustomize Forums Top

Seems to be working as intended on my computer, but I have no system tray icon. I'm pretty sure there were one on the last version.

Reply #8 from Stardock Forums Top

Quoting JanOscar, reply 7

Seems to be working as intended on my computer, but I have no system tray icon. I'm pretty sure there were one on the last version.

We have yet to put in a system tray icon.

There should be an option in future updates.

Reply #9 from WinCustomize Forums Top

Quoting Neil, reply 8

We have yet to put in a system tray icon.

There should be an option in future updates.
Great. Tried some different themes and changed settings all around, and so far so good.

Reply #10 from Stardock Forums Top

Quoting DaveRI, reply 6

Win10 v1909 build 18363.778

Ultimately a "nothing-burger" for me but I should mention it.  After installing this beta, the first time I applied a Curtains theme Explorer instantly went into a constant crash-reload loop, while the Curtains UI was still open, which I stopped by applying the Default theme once again.  After that, themes loaded fine.

I have had a crash-loop happen also, but only when playing with the Button.* advanced settings.  Adding a Button.Background image, for example, seems to do it every time.  I didn't mention it because I'm running Fences, ShadowFX, AeroGlass, Open Shell Menu, DisplayFusion, Groupy, etc, and didn't know if this was just a conflict with some other app that also messes with the Windows UI.  Now that I look, though, I did get a crashdump for explorer.exe in %LOCALAPPDATA%\CrashDumps , with the following stack trace:

Code
  2. STACK_TEXT: 
  3.  0x0
  4.  Curtains64!DrawSkinGroupy+0x58fe
  5.  explorer!TrayUI::WndProc+0x12e
  6.  explorer!CTray::v_WndProc+0xcbf
  7.  explorer!CImpWndProc::s_WndProc+0x78
  8.  user32!UserCallWinProcCheckWow+0x2bd
  9.  user32!CallWindowProcW+0x8e
  10.  comctl32!CallNextSubclassProc+0x89
  11.  comctl32!DefSubclassProc+0x77
  12.  inject!Init+0x1af9c
  13.  inject!Init+0x1aa2d

So it looks like maybe Curtains' DrawSkinGroupy function is missing a NULL function pointer check somewhere.

 

Reply #11 from WinCustomize Forums Top

Quoting Neil, reply 5

Please apply Windows 10 look in WB, ensure your colours are set normally (that's light grey for the background of that about box) and then apply curtains styles.
Oky dok. I was under the impression that applying Curtains would automatically "unapply" windowblinds.  So you mean to say I need to load the default MS skin in WB, then load Curtains?  Seems a pain in the arse, but I shall try it.

 

Reply #12 from WinCustomize Forums Top

Ok, I applied the default skin in WB. My text in the places list is still dark.  Even before Curtains. And I never change text colors. I run WB skins as they come, I don't tweak MS themes, etc.

 

Reply #13 from WinCustomize Forums Top

Ok, it was apparently that windows has "synced" a theme from another rig.  I set a default Winders 10 theme and all is well, so far.

Reply #14 from Stardock Forums Top

As I mentionet in the Beta 1 issue report treat, the descriptions in Edit Style -> Taskbar for the Start10 entry's are missing or wrong.
For example:

Description missing.

Description wrong. That's confusing.

I also think the drop down list needs to be re-ordered.

The "optional light mode" entry's should always be directly unter there standard entry's.

Reply #15 from Stardock Forums Top

Quoting dnelson_1901, reply 10


Quoting DaveRI,
reply 6

Win10 v1909 build 18363.778

Ultimately a "nothing-burger" for me but I should mention it.  After installing this beta, the first time I applied a Curtains theme Explorer instantly went into a constant crash-reload loop, while the Curtains UI was still open, which I stopped by applying the Default theme once again.  After that, themes loaded fine.



I have had a crash-loop happen also, but only when playing with the Button.* advanced settings.  Adding a Button.Background image, for example, seems to do it every time.  I didn't mention it because I'm running Fences, ShadowFX, AeroGlass, Open Shell Menu, DisplayFusion, Groupy, etc, and didn't know if this was just a conflict with some other app that also messes with the Windows UI.  Now that I look, though, I did get a crashdump for explorer.exe in %LOCALAPPDATA%\CrashDumps , with the following stack trace:

Code
  2. STACK_TEXT: 
  3.  0x0
  4.  Curtains64!DrawSkinGroupy+0x58fe
  5.  explorer!TrayUI::WndProc+0x12e
  6.  explorer!CTray::v_WndProc+0xcbf
  7.  explorer!CImpWndProc::s_WndProc+0x78
  8.  user32!UserCallWinProcCheckWow+0x2bd
  9.  user32!CallWindowProcW+0x8e
  10.  comctl32!CallNextSubclassProc+0x89
  11.  comctl32!DefSubclassProc+0x77
  12.  inject!Init+0x1af9c
  13.  inject!Init+0x1aa2d


So it looks like maybe Curtains' DrawSkinGroupy function is missing a NULL function pointer check somewhere.

 

Looking at it the issue is being triggered by you using OpenShell.  Which version of OpenShell are you using?

Also please don't use ShadowFX with Curtains as it is redundant given the shadow offerings in Curtains now.

Reply #16 from Stardock Forums Top

Quoting Neil, reply 15


Quoting dnelson_1901,
reply 10






Quoting DaveRI,

reply 6


Win10 v1909 build 18363.778

Ultimately a "nothing-burger" for me but I should mention it.  After installing this beta, the first time I applied a Curtains theme Explorer instantly went into a constant crash-reload loop, while the Curtains UI was still open, which I stopped by applying the Default theme once again.  After that, themes loaded fine.



I have had a crash-loop happen also, but only when playing with the Button.* advanced settings.  Adding a Button.Background image, for example, seems to do it every time.  I didn't mention it because I'm running Fences, ShadowFX, AeroGlass, Open Shell Menu, DisplayFusion, Groupy, etc, and didn't know if this was just a conflict with some other app that also messes with the Windows UI.  Now that I look, though, I did get a crashdump for explorer.exe in %LOCALAPPDATA%\CrashDumps , with the following stack trace:

Code
  2. STACK_TEXT: 
  3.  0x0
  4.  Curtains64!DrawSkinGroupy+0x58fe
  5.  explorer!TrayUI::WndProc+0x12e
  6.  explorer!CTray::v_WndProc+0xcbf
  7.  explorer!CImpWndProc::s_WndProc+0x78
  8.  user32!UserCallWinProcCheckWow+0x2bd
  9.  user32!CallWindowProcW+0x8e
  10.  comctl32!CallNextSubclassProc+0x89
  11.  comctl32!DefSubclassProc+0x77
  12.  inject!Init+0x1af9c
  13.  inject!Init+0x1aa2d


So it looks like maybe Curtains' DrawSkinGroupy function is missing a NULL function pointer check somewhere.

 



Looking at it the issue is being triggered by you using OpenShell.  Which version of OpenShell are you using?

Also please don't use ShadowFX with Curtains as it is redundant given the shadow offerings in Curtains now.

 

If it can help DaveRI and what Neil points out , I have no issue using curtains beta 3 with Classic Shell Menu 4.3.1 ( never used Openshell since CSM was left and open source. My rig : Windows 10 1903 ( 18362.628 ) x 64 - Maybe give a try for this 

Reply #17 from Stardock Forums Top

Quoting Neil, reply 15

Looking at it the issue is being triggered by you using OpenShell.  Which version of OpenShell are you using?

Also please don't use ShadowFX with Curtains as it is redundant given the shadow offerings in Curtains now.

It looks like some of my issues were a combination of all the other UI-tweaking apps I have installed.

To make debugging a little easier, I have uninstalled Aero Glass, Open Shell Menu, and ShadowFX.  I created a "broken" style by copying the Cairo Dark style, and editing the Button.Background setting to use the "start-button.png" image.  Now what happens when I click "Apply Changes" is this: the screen goes black for a second, and comes back but all the windows are back to the stock Windows 10 style.  After ~25 seconds, the screen goes black again, with only the mouse pointer visible.  Clicking doesn't seem to do anything, Alt-Tab shows the task list but doesn't seem to do anything else.  Tapping the Windows key a couple of times brings the desktop back, but the Start menu, taskbar, and desktop are hung, and all the window frames have an old pre-windows-10 theme:

Checking process IDs before and after the first flicker and the long back screen, it looks like dwm.exe has crashed and restarted both times.  If I go back to Curtains, select a working style, and kill dwm.exe again, everything goes back to normal.  No crashdumps seem to be generated, though.

Hopefully this will be enough info to let you reproduce it at your end.

Reply #18 from Stardock Forums Top

Win10 v1909 build 18363.815

I have been seeing this since I installed the first Beta. At first, the delay was not as long, but not it has gotten worse. When I close or minimize open windows, and end up at the desktop, the desktop is non-functional. I have WindowsBlinds, Fences, and Deskscapes running at the same time (all newest versions). Basically, I have to wait for the desktop to work again after I close the windows. Nothing works. No icons appear. I can't even get to the taskbar to get to anything on that. However, what is totally odd is if I maximize a minimized program window, these programs work fine . . . until I minimize or close said window. Then I am back to a non-functional desktop. Today, the delay was so long, I just rebooted and uninstalled the Curtains Beta (the one installed was the newest as I had been updating it to see if this problem went away.