Recommended Posts

Here's what that looks like added to the notifier. Is this what you mean? If not, please give me a screenshot so I can better understand what you're getting at.

That's exactly what I mean, but not only on the notifier, but in the main (covershade) window as well. That rectangle will be black or white depending on the text color (Light, non-light)

Thanks crimson.

Sorry FineWolf, but I really don't like the look of that rectangle. It takes away too much from the clearness of the skin. Adding it would be really easy, but it just doesn't look good to me. Of course you are free to modify your own copy of the skin and here's the line to add to the notifier if you need it:

<rect id="text.bg" x="10" y="19" w="0" h="37" relatw="1" color="255,255,255" filled="1" alpha="100" ghost="1" />

Put that in the "notifier.text" group.

Nice, the ol' guru meditation I presume? Which version (clear or not) are you getting the error with? And have you downloaded the latest build? I've changed a few things in the past few days, though the version number has not changed.

I noticed that i get the a/m script error when closing winamp via the windows task bar>r-click>close. :shiftyninja:

(using winamp 5.2)

Simplicity does not have a clear style squek, only SimplicityClear allows for alpha-blending. They are both the same skin, only one is clear and the other is not.

I noticed that i get the a/m script error when closing winamp via the windows task bar>r-click>close.

I've never had Winamp showing in the taskbar, only the system tray, but I just tried putting it there and closing it by right-clicking. However, I did not receive an error. Are you using a shell replacement (Litestep or blackbox) or Windowblinds or anything else? And are you using SimplicityClear or the normal version? I just need more info to help.

I've never had Winamp showing in the taskbar, only the system tray, but I just tried putting it there and closing it by right-clicking. However, I did not receive an error. Are you using a shell replacement (Litestep or blackbox) or Windowblinds or anything else? And are you using SimplicityClear or the normal version? I just need more info to help.

Apologies for that. Probability will be higher if i'm using winamp for quite awhile. As for shell replacement, just using heylove's vs. A couple of pages back i posted a screenie of my desk. It's still the same. Using clear btw.

Ok thanks, that helps. I'll leave Winamp open and playing for the next couple hours and see if I can reproduce that error. BTW, do you have any third-party plugins installed? Sometimes they can cause crashes. I only have the Dynamic Library installed, but I'd like to install what you have as well.

Hey Axialix, first of all, seriously, this is an excellent skin. Been looking for years for a simple yet thoroughly smooth looking skin, and here it is! Usually with good skins I find something I don't like about the design or something that I'd like to see included, but so far this one is just the ticket. (Give it time!)

Couple of issues though. Don't want to call them bugs as I may just be missing something. The main one is that when winamp is minimised (to the systray only), and a track changes, as well as the notifier appearing, the main winamp window reappears. It then cannot be minimised (minimise button does nothing) and is stuck on screen. The only way to get rid is to close winamp and reopen, then the minimise button works fine, until the next track change and here we go again. Annoying I'm sure you'll agree. Have you noticed this, or is it something I am doing/not doing? More info: if any other windows were active before I minimise for the first time (like the playlist window), these do not reappear on track change: just the main window appears on it's own.

The second is a minor annoyance. When I resize the width of the playlist window to be the same as the default main winamp window width, when i hide and then reshow the playlist window it does not rememeber the new width setting, and defaults back to being wider than the main window. Any ideas?

I used (and use!) all your skins: good, better, best! Thank's for that.

I just noticed a bug using Simplicity Clear: time to time, when opening Winamp, loading folder or what else... the main and PL windows change place. 2 days ago Winamp was completely out of screen...

Any idea? :blink:

edit: Just a detail: I use the Shade mode...

The main one is that when winamp is minimised (to the systray only), and a track changes, as well as the notifier appearing, the main winamp window reappears. It then cannot be minimised (minimise button does nothing) and is stuck on screen.

Yep, that just happened to me too. Strange, the things you never check because you don't use them. I've never used the minimize feature, honestly I really haven't. Ok, well I assume this is all because of the notifier, so I'll try to get it fixed soon.

The second is a minor annoyance. When I resize the width of the playlist window to be the same as the default main winamp window width, when i hide and then reshow the playlist window it does not rememeber the new width setting, and defaults back to being wider than the main window

Weird, I can't reproduce this one. You have yours setup something like the pic below yeah?

I just noticed a bug using Simplicity Clear: time to time, when opening Winamp, loading folder or what else... the main and PL windows change place. 2 days ago Winamp was completely out of screen...

You have the main shade mode docked to the playlist correct? Or are you using the playlist shade mode?

Sorry for so many questions, but it really helps to know exactly how you all have winamp configured. Thank you both for the bug reports. I'll do my best to get things corrected for you.

post-110624-1145639454.jpg

Minimize problem should be fixed now namefake. Thanks very much for posting it. I would never have known otherwise.

I'm still trying to get that playlist width problem to appear, but no luck so far. Do you have the PL visualizer turned on? If it's off, the minimum width is shorter, but I don't see how this could affect the show/hide behavior you mentioned.

When I resize the width of the playlist window to be the same as the default main winamp window width, when i hide and then reshow the playlist window it does not rememeber the new width setting, and defaults back to being wider than the main window

Got that fixed too. Finally noticed it when I reloaded the skin a few times.

xelios, I'm still looking for the window displacement you mentioned. I'll see it eventually I guess...

Interesting setup xelios, looks nice. I'll configure mine the same way and try to catch the movement. You've given me enough to go on though.

<edit> Yep, just saw it. The playlist moved about 20 pixels left when I resized the main window. Can you try not docking the two windows together? Just separate them by a few pixels, that should be enough that they don't interact. Don't know if you've tried that already, but it should be a quick fix for the moment. </edit>

Edited by axialix

Damn, I don't know why I didn't think of this before, why don't you turn on the Freeze option? That would pretty much stick it to the desktop where it would be unmovable. Or am I wrong in assuming that it's not you that is causing the movement, it's other windows/apps?

Further to the script errors, I just got this one after closing Winamp from the tray. As far as I can tell, it works fine when closed using the button on the skin, but sometimes crashes when closed from the systray.

If it helps, I was playing music when I closed it, and it had been open for a few hours. Plugin wise, I have the following installed (extra):

  • Dynamic Library
  • Jump To File
  • DoJoe's Screen Lock Detector
  • Live Messenger Status Plugin v0.23
  • SleepTimer
  • Tips
  • and Toaster (don't use built in toasts)

post-59451-1145707939_thumb.jpg

** Edited to get decent quality pic, first one was really, really bad **

The Freeze option was on but I had to turn it off because I often have to replace Winamp at the right place. I think no other window is making winamp to move because all the windows of all my programs never go over the Winamp area, or the desktop icons at right. Approximately in the square you can see in the screenshot below (example with Firefox in the second one):

untitled16vy.th.jpg

untitled27av.th.jpg

I'm trying a space between main and playlist...

Edit: I have bad news: using a space between the main and PL windows (shade) doesn't fix the problem... And my god it seems I'm alone with this...

Appreciate you taking the time to explain the problem so well Sмεη. It's been happening to me too, I just can't understand why it only does it from the systray or taskbar. ?

:) No xelios, you're not alone. I've seen it happen too. I don't have it fixed yet, but I am working on it.

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

    • No registered users viewing this page.
  • Posts

    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
    • I think he means you haven't reviewed previous UFC games. Of course it doesn't matter... Every time you just report on something that involves the President even if just simply what happened you guys usually get accused of being anti-Trump. We live in fun times.
  • Recent Achievements

    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      78
  • Tell a friend

    Love Neowin? Tell a friend!