Skip to main content

Topic: foo_title, new version for 0.9 (Read 215665 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
foo_title, new version for 0.9
Reply #100
I'd suggest using a fixed-widt font for that, personaly.

Yes, I already tried some (system, Terminal), but they must be incompatible with this component display (not true type ones?). Could you recomment some ones in particular ?

  • Ken-chan
  • [*]
foo_title, new version for 0.9
Reply #101
I'm sorry, I don't know of any myself. Perhaps it would be wise to make a test version, then, where you use a bunch of W's (they're the widest, afaik) and let that be the maximum amount, so that there is no problem with the rest of the strings you could possible think of?

You may be able to find a fixed-width font on the web for free, try googling it?
There's a storm on the loose, there's sirens in my head...

foo_title, new version for 0.9
Reply #102
I'm sorry, I don't know of any myself. Perhaps it would be wise to make a test version, then, where you use a bunch of W's (they're the widest, afaik) and let that be the maximum amount, so that there is no problem with the rest of the strings you could possible think of?

It's the workaround I'm currently using. The problem (could we really call this a problem ) is that whenever a shorter (in pixels) title appears, it is truncated (word+"...") and appears very small in the quite large layer...

Quote
You may be able to find a fixed-width font on the web for free, try googling it?

I'll do that
  • Last Edit: 15 August, 2006, 11:07:19 AM by jon.schaffer

  • Quiark
  • [*][*][*]
foo_title, new version for 0.9
Reply #103
Courier, Lucida Console are fixed-size. I'm not likely to implement elipsized text support.

Now I have little free time to implement anything

foo_title, new version for 0.9
Reply #104
Courier, Lucida Console are fixed-size. I'm not likely to implement elipsized text support.
Thanks. For a reason, Courier doesn't work for me. Lucida Console works fine.

Quote
Now I have little free time to implement anything
It's already such a good component, offering so many possibilities... Thanks!
  • Last Edit: 16 August, 2006, 04:31:01 AM by jon.schaffer

  • Sw!ng
  • [*][*]
foo_title, new version for 0.9
Reply #105
Ok,
where 's the "Off-Button" ...??

(I realy like this component, but I dont need it always and removing,restart,inserting,restart,... cant b the solution !! )

  • Quiark
  • [*][*][*]
foo_title, new version for 0.9
Reply #106
Properties - foo_title - Show foo_title when: Never should be enough.

  • Sw!ng
  • [*][*]
foo_title, new version for 0.9
Reply #107
... Should be ...!! 

But how could I know that I didnt had the latest version ...??
-I mean there was no "foo_title.dll" in the Components-Versions ...
(Well, and "managed wrapper" wasnt realy associateable for me)

But THANX, so far !!
(you should rename the components  )

  • Quiark
  • [*][*][*]
foo_title, new version for 0.9
Reply #108
These names have their meaning (see one of the posts on the first page of this thread). I'll add version info to the property sheet. Anyway, you can see the version when you find the dotnet_title.dll in Explorer, right click and select Properties

  • vlada
  • [*][*][*][*]
foo_title, new version for 0.9
Reply #109
Hi,
I'm working on my own skin. I'd like tosk you, if it is possible to add a volume and graphical time played indicator. So I need to use variables in some elements positioning. If it is possible to do it, can you give me some directions how, please?

Also where can I find which commands and which variables for text displaying I can use? Is it everything what TAGZ syntax allows?

Thank you.

foo_title, new version for 0.9
Reply #110
I downloaded the component and put all the appropriate .dll files in the components folder.  However, I get a series of errors because the remaining .xml files and corresponding .png files are not in the right folders.  The download does not include a readme file to explain what files go in what folders.  I checked the documentation page and it only indicated where the .dll files go and not the remaining files.  I have after scouring this thread managed to figure out that two additional folders need to go in the root directory of foobar titled "white" and "another", and each of these folders must contain the corresponding .xml file.  However, I have no idea where the remaining .png files are supposed to go?  Can someone post exactly where all the files from the download of this component are supposed to be placed?  Thanks.

  • Ken-chan
  • [*]
foo_title, new version for 0.9
Reply #111
You got a download that was setup to be extracted into your main foobar folder, with directories ON.

There will be a new folde rin your Foobar folder, called foo_title. In there, for every skin you download, there will be another folder, with the name of that skin in it. In that folder, the .xml file and the images will be stored.

The .dll files are set up to go into your components folder, as normal components do.
There's a storm on the loose, there's sirens in my head...

  • Quiark
  • [*][*][*]
foo_title, new version for 0.9
Reply #112
Hi,
I'm working on my own skin. I'd like tosk you, if it is possible to add a volume and graphical time played indicator. So I need to use variables in some elements positioning. If it is possible to do it, can you give me some directions how, please?

Also where can I find which commands and which variables for text displaying I can use? Is it everything what TAGZ syntax allows?

Thank you.


Volume and time played sliders are not possible at the moment. Commands are the main-menu commands, so it can be anything like "Play", "Stop after current", "Cut tracks" and so on. It should be possible to use anything from TAGZ, including functions.


I downloaded the component and put all the appropriate .dll files in the components folder.  However, I get a series of errors because the remaining .xml files and corresponding .png files are not in the right folders.  The download does not include a readme file to explain what files go in what folders.  I checked the documentation page and it only indicated where the .dll files go and not the remaining files.  I have after scouring this thread managed to figure out that two additional folders need to go in the root directory of foobar titled "white" and "another", and each of these folders must contain the corresponding .xml file.  However, I have no idea where the remaining .png files are supposed to go?  Can someone post exactly where all the files from the download of this component are supposed to be placed?  Thanks.



You must be using some strange program as the .zip has just the right directory structure. Anyway, see this listing:

Code: [Select]
foobar2000-0.9/components:
dotnet_title.dll
foo_managedWrapper.dll

foobar2000-0.9/foo_title:
another - folder
white - folder

foobar2000-0.9/foo_title/another:
down_03.png
..more .png images..
skin.xml

foobar2000-0.9/foo_title/white:
skin.xml
..more png images..

  • malde
  • [*]
foo_title, new version for 0.9
Reply #113
would be great if one would be able to pin the skin or controlpanel to the desktop.
that'd offer the possibility to use the plugin as a widget like thingy

foo_title, new version for 0.9
Reply #114
For animations: what is the duration of a single image?

  • Quiark
  • [*][*][*]
foo_title, new version for 0.9
Reply #115
would be great if one would be able to pin the skin or controlpanel to the desktop.
that'd offer the possibility to use the plugin as a widget like thingy


Yep, that shouldn't be difficult to do.

For animations: what is the duration of a single image?

Next image is used every update (so it depends on the update interval set by user).

  • rouge
  • [*][*][*]
foo_title, new version for 0.9
Reply #116
I'm starting to really like this plug-in.  I accidently posted it in the 3-year-old thread.

I have a request.  It already has always on top feature, but I would like it to stay on top and not have it overlap maximized windows. That is, they would maximize normally, but not all the way to the top where i have my skin going all the way across.  Thanks in advacnce.

  • Sphix
  • [*][*][*]
foo_title, new version for 0.9
Reply #117
Very nice plugin, thanks!
-foobar2000 + Burrrn + EAC
-HD 80Gb using High QualityVBR MP3s

  • Chaser
  • [*][*][*][*]
foo_title, new version for 0.9
Reply #118
This component is great. Thank you for creating it! I'm just testing, whether it can replace AMIP for me..

  • Sphix
  • [*][*][*]
foo_title, new version for 0.9
Reply #119
Feature Request:
- Disable "Always on Top" function

-foobar2000 + Burrrn + EAC
-HD 80Gb using High QualityVBR MP3s

foo_title, new version for 0.9
Reply #120
Does plug-in work for anybody in 0.9.4 beta? I keep getting NET Framework pop-up and don't know of a  way to kill it. 2.0 is installed.  I deleted .dll and related folders from component directory but when I click through NET warning I still end up with config panel of the plug-in. I rebooted so it's not cache.

Any tips?

Edit
I overlooked a .dll in component directory so no more pop-ups. Looks like a cool plug-in but does it work under beta 0.9.4?
  • Last Edit: 14 September, 2006, 11:33:48 PM by trackfan504

  • neothe0ne
  • [*][*][*][*]
foo_title, new version for 0.9
Reply #121
I was wondering if you could add an option to ONLY show foo_title when foobar is BOTH playing a song AND minimized.  Currently, you can make it show when foobar is minimized, but if no song is playing it shows an empty box and tends to get in the way.  I'd appreciate it if you could add this option!

  • Quiark
  • [*][*][*]
foo_title, new version for 0.9
Reply #122
Does plug-in work for anybody in 0.9.4 beta? I keep getting NET Framework pop-up and don't know of a  way to kill it. 2.0 is installed.  I deleted .dll and related folders from component directory but when I click through NET warning I still end up with config panel of the plug-in. I rebooted so it's not cache.

Any tips?

Edit
I overlooked a .dll in component directory so no more pop-ups. Looks like a cool plug-in but does it work under beta 0.9.4?


I just tried it under foobar2000 0.9.4 beta 3 clean installation and it works ok..

I was wondering if you could add an option to ONLY show foo_title when foobar is BOTH playing a song AND minimized.  Currently, you can make it show when foobar is minimized, but if no song is playing it shows an empty box and tends to get in the way.  I'd appreciate it if you could add this option!


Yes, I probably could

Disable always on top will be in the next release as well

However I have no idea how to implement the docking (as rouge suggests)..

foo_title, new version for 0.9
Reply #123
Ok, I asked a while back about a framework 1.1 build, but have since installed VS 2005, so it's a moot point.  Let me just say that I love this component!  I have looked over the skins and really didn't see anything I like, so I'll have to work on that, but I had a couple requests.  Can you add tooltips to buttons?  Can you add a tooltip to the song text (so, to a text or scrolling-text layer) that can be formatted with TAGZ.  This would let me hover over the song title to see year and album info and such.  I know the skin could just show it, but I like it to be standard Windows titlebar sized.  Finally, I think a customizable right-click menu would be great.  You mentioned that you don't have time, and I was also wnodering if the source was available so I could work on it myself?  Thanks for making such a great component already, these are just minor suggestions!

  • Cosmo
  • [*][*][*][*][*]
foo_title, new version for 0.9
Reply #124
Thank you Quiark, this component is very useful and you're doing a great job with it.

Figuring out which actions are able to be assigned to buttons is difficult. Your web page says ''It can be any command from the main menu, like Play.'' Should that mean that all commands found here should be available? I know (or it seems) that not all of them are able to be used right now, but I'm wondering if that's just because your component needs to catch up with recent foobar updates? Will the usable actions/commands be expanded, perhaps to include all of the above mentioned list of menu items (/or command line switches)? Lastly, is there an easy way to list all the actions which are usable, or is trial-and-error the only way?

Thanks!
  • Last Edit: 26 September, 2006, 10:32:31 PM by Cosmo