Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foo_prettypop (Read 439361 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foo_prettypop

Reply #25
Quote
You'll have to do it eventually anyway as .net is gradually replacing win32.
[a href="index.php?act=findpost&pid=290386"][{POST_SNAPBACK}][/a]


Haw. It'll be a hell of a long time before that happens. Look how long it took Microsoft to drop DOS on its workstation-level OSes. Didn't happen until Windows XP.

foo_prettypop

Reply #26
Hello again everyone. Thanks for all the feedback. I’ve released a 1.0.4 with many new features:

New in 1.0.4:
Enable or disable album art
Enable or disable “last resort” image finding
Option to disable the ‘hover’ effect (default is off now, actually)
Option to disable the titlebar (picture of this mode now in original post, no move support yet, but location is same as when titlebar was on)
Set the target opacity to fade-in to
Set an optional background color
Option to never fade-out
Different behaviors when clicking on popup (current options: do nothing, skip to next track, show main foobar2000 window, and hide the popup immediately)

Bugfixes:
Tried again to clean up startup code so no crashing. Effects of this are uglier default fonts.
Release the file handle to the album picture after song is done playing. This should fix the issues of not being able to rename, move, etc a file or folder even after the song is over.
Many smaller fixes to various areas to try to solve other crashes posted in this thread.
More Unicode fixups.

Changes:
Album art TAGZ expressions are now always required to be absolute paths.

Standing bugs:
After pulling up the configuration and changing some settings, the first popup will be woefully wrong (to put it simply). Sometimes it steals focus, other times it’s sized wrong, etc. This only happens the first time after adjusting some settings, and doesn’t clobber your position settings.
Fonts not installed in the Windows fonts directory will likely crash the program if selected (possible .NET bug).
Hover mode is still shoddy and now disabled by default (in particular, switching between titlebar and no titlebar really messes it up!)
Tabstops are completely messed up in config. Strange issue.
Having .NET 2.0 beta installed will break it. This is a MUCH more serious issue than first found out to be. I don’t know what the problem is, beta 2 is due out this month, so I’m going to wait for that before going into panic mode.

As always, please share your comments both good or bad. Thanks!

foo_prettypop

Reply #27
Awesome plugin! I have been using the on screen display plugin, but I have since replaced it completely with pretty popup. So far I haven't had any problems, but here are some suggestions I thought of:

1. When the titlebar is hidden, I'd prefer not to have round corners on the popup window. Perhaps the option to choose more display features, such as rounded corners, window border, etc. could be offered.

2. As others have already mentioned, I'd appreciate the ability to use TAGZ to customize the text that gets displayed.

Other than that, I love it. Thanks a bunch, FrozenSpoon, and keep up the good work!

foo_prettypop

Reply #28
Quote
Quote
You'll have to do it eventually anyway as .net is gradually replacing win32.
[a href="index.php?act=findpost&pid=290386"][{POST_SNAPBACK}][/a]


Haw. It'll be a hell of a long time before that happens. Look how long it took Microsoft to drop DOS on its workstation-level OSes. Didn't happen until Windows XP.
[a href="index.php?act=findpost&pid=290643"][{POST_SNAPBACK}][/a]


I don't believe any workstation versions of Windows ever had DOS. At least NT 3.5 had no DOS as of 1994. Do you mean home OSes? 

Even so, supporting one API does not preclude requireing another.  Windows 95 may have supported DOS apps, but good luck running Windows programs on DOS.  Likewise Windows XP supports DX6 games, but you can't play Far Cry without installing DX9.  In much the same way, .net will be required to run mainstream applications many years before Win32 support is discontinued (assuming it ever is).  Eventually everyone will have .net, either because they installed it themselves, thier software installed it for them, or because they bought an OS that comes with it preloaded.  So you may as well bite the bullet and install it now if you want to use software that requires it.

foo_prettypop

Reply #29
no such luck yet...  gave me the same ol' error:
Code: [Select]
Illegal operation:
Code: C0000005h, flags: 00000000h, address: 06000091h
Access violation, operation: read, address: 06000091h
Call path:
WinMain=>app_init
This is the first crash logged by this instance.
Access violation, operation: read, address: 06000091h
Stack (0012FB00h):
0012FAE0h:  77F98191 77F89650 FFFFFFFF 00E7D83C
0012FAF0h:  7C59F573 00070000 00000000 02BC1260
0012FB00h:  00401523 00444248 014F0000 007E6CF8
0012FB10h:  007E6AD8 007E6D40 0043946C 007E6B00
0012FB20h:  0000003E 0000003E 00000000 00000033
0012FB30h:  00000022 007E7230 013E02E0 007E6FB8
0012FB40h:  0012FB84 00401443 014F0000 0012FC04
0012FB50h:  007E6CF8 78001DB0 00000000 0043946C
0012FB60h:  007E6C88 00000028 00000028 00000000
0012FB70h:  00000021 00000017 007E6AD8 00000004
0012FB80h:  007E6D40 0012FC14 004017F8 007E6B58
0012FB90h:  0012FC04 0043946C 00000000 78001DB0
0012FBA0h:  0043946C 007E6BA0 00000036 00000036
0012FBB0h:  00000000 00000025 FFFFFFFF 0012FC04
0012FBC0h:  78001E00 007E0000 00000000 007E6B00
0012FBD0h:  0043946C 0000C107 78001DB0 0012FC14
0012FBE0h:  100022F7 0043946C 77E2726F 77E27277
0012FBF0h:  0012FBF4 0012FFB0 7800BD6A 780322A0
0012FC00h:  FFFFFFFF 014EB4CC 100059BF 007E6B00
0012FC10h:  004329DC 0012FF0C 004113C7 007E6B58
Registers:
EAX: 014F82C3, EBX: 007E7230, ECX: 0012FFB0, EDX: 77FCF348
ESI: 014F0000, EDI: 007E6FB8, EBP: 0012FB40, ESP: 0012FB00
Failed to get module/symbol info.

Version info:
foobar2000 v0.8.3
UNICODE

foo_prettypop

Reply #30
hmm, slight bug with the new version.  If the fade-in time is set to "0.00s", then the popup will never disappear.

Other than that, great work.  I like being able to remove the titlebar.

foo_prettypop

Reply #31
Quote
hmm, slight bug with the new version.  If the fade-in time is set to "0.00s", then the popup will never disappear.
[a href="index.php?act=findpost&pid=290972"][{POST_SNAPBACK}][/a]

Oops, fixed. Didn't bump the number but the copy on the webpage is fixed.

foo_prettypop

Reply #32
I like this one! I do have a request however.

When it is showing the titlebar. The title bar is showing the inactive colors.
Mostly grey or greyed out. Could there be an option to show the "active titlebar" colors?

It would be the same as the winamp option, "Do not dim inactive titlebar.
I hope I am making any sense here.

Thanks for making foo_prettypop!

foo_prettypop

Reply #33
%_filename% no longer works in the new version as a Filenames option .. was working in 1.03.  Great plugin!

foo_prettypop

Reply #34
it's look great, i give it a try.
i'll come back later for feedback

foo_prettypop

Reply #35
Bug report:
Trying to change the "Title" font always gives a .NET exception, saying that the selected font is not a TrueType font, and the system supports only TrueType fonts. (Translated by myself from the localized exception message). I have .NET 1.1, localized to Hungarian. All Pretty Popup settings are on default.
I can change all the other fonts though, and all are Arial (which is an OpenType(?) font, not a TrueType font, anyhow)
And when I push play, the foobar window disappears without any error message.
Life is Real...
(But not in audio :) )

foo_prettypop

Reply #36
Like already said, it would be nice if there were no round corners when the titlebar is hidden. I'd prefer only a square (perhaps with a configurable edge).

I actually think that both of these following "bugs" weren't in the first version, but I'm not 100% sure.
1) I also have the problem with the titlebar showing in inactive colors, unless I click on it.
2) When using a theme that fakes the titlebar height by having transparent pixels on top of it, foo_prettypop shows them as black, not trasnparent.

foo_prettypop

Reply #37
Quote
%_filename% no longer works in the new version as a Filenames option .. was working in 1.03.  Great plugin!
[a href="index.php?act=findpost&pid=291003"][{POST_SNAPBACK}][/a]


FrozenSpoon stated when he posted 1.0.2 that if you use TAGZ expressions as a filename, you have to give the absolute path.  That means you'll want an expression like this:

Code: [Select]
$replace(%_path%,'.'$ext(%_path%),)


instead of %_filename%

foo_prettypop

Reply #38
Quote
FrozenSpoon stated when he posted 1.0.2 that if you use TAGZ expressions as a filename, you have to give the absolute path. 


He sure did .. I wasn't even paying attention.  Thanks!

foo_prettypop

Reply #39
Quote
When it is showing the titlebar. The title bar is showing the inactive colors.
Mostly grey or greyed out. Could there be an option to show the "active titlebar" colors?
[a href="index.php?act=findpost&pid=291002"][{POST_SNAPBACK}][/a]

I'm not too sure at the moment how to fix this... I'm just using a standard 'tool' window provided by Windows, and the only way I could show it as active would be to steal focus. Winamp uses skins so it has complete control over every pixel. I'll see if it's possible, not too sure about it though.
Quote
Bug report:
Trying to change the "Title" font always gives a .NET exception, saying that the selected font is not a TrueType font, and the system supports only TrueType fonts.
[a href="index.php?act=findpost&pid=291010"][{POST_SNAPBACK}][/a]

Is it only one font that this happens with? Does it happen if you try to select the same font for any of the 4 selections? I do know that if a font is not installed in the Windows "fonts" directory (example- Windows\fonts), I get this error too. Fonts can be installed anywhere on the machine if they are registered correctly, but apparently this is breaking one call I make in .NET. If this is the case, you may want to try moving the font file to the Windows\fonts directory. Then (after backing up the file just in case..), delete it from the orginal location and restart foobar2000. As long as its in that windows\fonts directory it should work (at least, if it was the same error I was getting). Until I figure out a better way of "remembering" the font selections... I have to rely on this old crusty method.

General consensus is rounded corners aren't needed, so I'll put out another version shortly that gets rid of this. They may be causing the problem anza reported even when not turned on (titlebar mode) so they may just have to go all together without leaving an option for them.

Allowing full control over the text with TAGZ is coming, but that'll be next week most likely. For those who are keeping it up all the time, I want to ensure dynamic information will work correctly.

Thanks for the feedback!

foo_prettypop

Reply #40
Looks like a good plugin.........
Probably a stupid question but why is .NET needed?
Is there no way of getting round this as I don't want to install it!

(Takes cover behind a wall)

foo_prettypop

Reply #41
.NET Framework is required to use software which is developed using .NET Managed languages. The only way around this is to redevelop without using Managed mode or classes.

foo_prettypop

Reply #42
There's no reason not to install the .net framework. It's small and doesn't interfere with anything.

foo_prettypop

Reply #43
Quote
Quote
Bug report:
Trying to change the "Title" font always gives a .NET exception, saying that the selected font is not a TrueType font, and the system supports only TrueType fonts.
[a href="index.php?act=findpost&pid=291010"][{POST_SNAPBACK}][/a]

Is it only one font that this happens with? Does it happen if you try to select the same font for any of the 4 selections?


Actually I have no idea which font is selected, as I get this exception by simply clicking on the "Change font" button in the prettypop preferences page. (Sorry for not being clear on this). No other option seems to cause this problem. I will try to track this down though, but frankly I don't know how to 

Edit: hmmm, could someone tell me the default font foo_prettypop uses for title? Maybe I don't have that font, or something...
Life is Real...
(But not in audio :) )

foo_prettypop

Reply #44
Quote
.NET Framework is required to use software which is developed using .NET Managed languages. The only way around this is to redevelop without using Managed mode or classes.
[a href="index.php?act=findpost&pid=291141"][{POST_SNAPBACK}][/a]

Thx for the reply.......havent gotta clue what you mean    but thx anyway 
No seriously I get the gist...

foo_prettypop

Reply #45
Quote
There's no reason not to install the .net framework. It's small and doesn't interfere with anything.
[a href="index.php?act=findpost&pid=291152"][{POST_SNAPBACK}][/a]


Ok I havent checked it out properly, when I checked it quickly it put me off.
Thx for the info I might install it.

foo_prettypop

Reply #46
I silently updated the copy on the webpage to not use rounded corners because it was creating some issues and many didn't really seem to like them that much anyways

Unless there are some more small issues, this will be the last version for awhile as I'll be pretty busy. However I do have some updates planned for 1.1, in particular:
Full TAGZ support for the text (no inline colors, maybe 1.2)
Album art on left or right
Proper "growing" if window is on left of screen
Better support for having the popup up all the time
New font system since the current one breaks so much (this is FINALLY done, I might be PMing some people to try it out)
Two shortcut keys
Move the popup in borderless mode

Yes, if you've been watching this, I've trimmed the features for the new release a little. I was starting to get concerned with feature creep. In particular, displaying the song info on the desktop required so much of a change in design, it's better off left to another plugin. This will remain a true 'popup'. Gray items are ones that are done so far.

foo_prettypop

Reply #47
Sounds good to me FrozenSpoon. I'll be waiting for v1.1

foo_prettypop

Reply #48
I'm glad you're already working on that "snap to desktop" feature since that was the first thing I was going to ask for!  Nice work.

foo_prettypop

Reply #49
Works, but as .net crap requires a super computer rather than my p3/500 and it pulls down complete fb2k startup etc. I will not use it. OMG it feels like java

But beautiful indeed.