Recommended Posts

QUOTE (Psychoticdemento @ Feb 2 2004, 09:08)

jezuz alanzeino....there are bugs in the screenshot!!

cmon...make the VS before u release.

1. the color and size of the bar on the inactive window are wrong and not connected

2. the tab is way to the right

didn't you read what alan wrote?

yes i read what he wrote...they arent "features," they are bugs becuase of a lazy themer.
QUOTE (Psychoticdemento @ Feb 2 2004, 00:08)

jezuz alanzeino....there are bugs in the screenshot!!

cmon...make the VS before u release.

1. the color and size of the bar on the inactive window are wrong and not connected

2. the tab is way to the right 

Seriously, how much time do you really spend looking at the display properties?

I think it's minor, and I say hell of a good job. Keep up the good work.

u sir, are a moron. inactive windows dont only show up in the display properties menu. and the tab thing is easy to fix, it would have taken a GOOD themer maybe 5 minutes. ah F*** it ill fix it myself.

Settle down, big guy. I mean, I doubt everything can live up to your apparent high standards. Just let the guy be.

Anyway, onto some good criticism meant in not a jackass way. I do think there are a few bugs that need to be worked out. For instance, the attachement shows the craziness that comes when using Trillian. Just thought I'd point it out.

post-36-1075775729.jpg

jezuz alanzeino....there are bugs in the screenshot!!

cmon...make the VS before u release.

1. the color and size of the bar on the inactive window are wrong and not connected

2. the tab is way to the right

LOL. From what I know, all themes are like that on the first tab when it isnt selected. The only reason why it sticks out is because I didnt put a dark border at the top of the frame.

And I added a beta start button into the extras because some people wouldnt like the new start button. The start button in the extras folder was actually the one I was going to release v4 with, but I chose not to. But ill upload a new update (vFOURpointONE) with extra start buttons, and a darker panel edge for you, picky ******. And the inactive window IS FINE ON MY pc, so it aint my fault if ur running xp on a p1. LOL, j/k ill see wat i can do.

Finally, I would like you all to know, that when I started work on the souluna style, the msstyle file was so fukd up, that a lot of bugs were im possible to fix. I had to just hide most of the bugs using some experimenting, so I dont appriciate the criticism, because this wasnt a new clean theme made in stylebuilder it was ported in windowblinds/skinstudio by msbmsn, and came out very bad. And if you want proof, open up the original souluna post in stylebuilder and try to edit those windowbar edges and see what happens.

I've been a big fan of this VS from the start... even when "the one that shall not be named" started it, and I'm glad that you took it over. But there's still a few major problems here.

1. Start bar gradient is still "not quite right"

2. Fonts = What fonts are used for the VS?

I'm running a monitor at a res of 1400 x 1050, and the visual style is unusable. I can go and change the fonts, etc, but it would be nice to be able to use the VS default, the way it was intended.

You've done an awesome job, and I love the style, but there's still some bugs there. Check the screen shot.

post-36-1075968130.jpg

Problem in Visual Studio, the find window is missing it's lower border...

Actually, this is an issue with LOTS of palettes (sp?), especially in Adobe products. I really liked the style, had it all set up, then got to work only to find that all of the lower borders of my Illustrator palettes were cut off - couldn't work like THAT!! :no:

Besides this bug, I like it a lot...

I found that I can't figure out why my trillian turned out like it did. It's good now. Probably just the initial applying of the visual style. I really like it. I do think that the clock's glow is a little unusual or hard to read at times. Just something I've noticed, but I still like it a lot. It's my current VS.

I've been a big fan of this VS from the start... even when "the one that shall not be named" started it, and I'm glad that you took it over. But there's still a few major problems here.

1. Start bar gradient is still "not quite right"

2. Fonts = What fonts are used for the VS?

I'm running a monitor at a res of 1400 x 1050, and the visual style is unusable. I can go and change the fonts, etc, but it would be nice to be able to use the VS default, the way it was intended.

You've done an awesome job, and I love the style, but there's still some bugs there. Check the screen shot.

I need you to explain wats goin on the the screny, i cant make out what you have a problem with. And I have a bad monitor that shows everything darker than it is so the gradient problem isnt visible for me

I need you to explain wats goin on the the screny, i cant make out what you have a problem with. And I have a bad monitor that shows everything darker than it is so the gradient problem isnt visible for me

Sorry Alan, I thought the screenie might have been enough... :blush:

1. If you enlarge the screenie you'll notice that on the start menu... the "P" for "system Preferences" has a line running thru it... the underscore has gone askew

2. The gradient on the start menu... that "demarkation" line thru the middle of it... that type of "gloss shadow/highlight" might look great for a start button, etc... but for a start menu panel it looks rather odd... it looks like 2 completely different colors instead of being a "blend"

3. The FONTS... I run a monitor at 1400 x 1050 (19") 24 bit color (nvidia FX5600 256 meg), the fonts appear very very small. I have no problems with other VS's as the fonts "scale" themselves to the resolution of the monitor.

Sorry to be a pain :cry:

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

    • No registered users viewing this page.
  • Posts

    • JetBrains launches Rider 2026.2 EAP 5, bringing several AI improvements by David Uzondu JetBrains has released the fifth EAP version of Rider 2026.2, bringing a faster startup flow with the new non-modal startup screen and quality-check hooks for Claude Code and Codex. In the latest EAP release, Rider now has newly bundled "quality-check" hooks that run background tests on code edits before the external agent proceeds. For example, after Claude Code rewrites a class, Rider immediately triggers a PostToolUse hook that analyzes the code for syntax errors and formatting warnings. It then passes those findings back to the model as feedback, allowing the agent to fix its own output before finalizing the task. If Rider detects compilation errors, the IDE prevents the agent from treating the task as complete, while minor formatting warnings simply help guide the model toward better output. The "Explain with AI" feature can now tackle tricky build errors directly from the console, helping .NET developers who frequently wrestle with multi-targeting failures and MSBuild errors. JetBrains introduced Explain with AI back in the 2024.1 release cycle. With this feature, instead of forcing developers to copy long diagnostics into a separate chat window, Rider now lets you trigger these explanations directly from the error source. In similar EAP news, JetBrains recently opened the first EAP for IntelliJ IDEA 2026.2, with features that appeal to both those who are into AI-assisted coding and those who prefer "classic" manual development. For manual developers, the release adds revamped dependency completion for Maven and Gradle build scripts, which pulls data directly from the local cache to suggest relevant versions. It also brings the Spring Debugger update, displaying security indicators next to endpoints to visualize secured routes during runtime. In addition to database migration tools for Flyway and Liquibase, this build introduces a Hibernate debugger that shows the exact SQL or HQL queries that the framework plans to execute, letting developers jump directly to the Java code that triggered them.
    • I have updated my Series 9 Watch so I assume there is either a mistake in what was said, or as suggested - the new AI feature set isn’t supported on anything other than those listed above.
  • Recent Achievements

    • Very Popular
      Captain_Eric earned a badge
      Very Popular
    • One Month Later
      amusc earned a badge
      One Month Later
    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
  • Popular Contributors

    1. 1
      +primortal
      502
    2. 2
      PsYcHoKiLLa
      222
    3. 3
      ATLien_0
      87
    4. 4
      Steven P.
      80
    5. 5
      +Edouard
      80
  • Tell a friend

    Love Neowin? Tell a friend!