HydrogenAudio

A bit resource heavy here. Uses 15-100% cpu with std look.  XP1500+.
Looks neat tho 

looks great, very nice, thanks !

for danz look: would it be easy to add a close button ? to save the currently used size on foobar close ?

and overall, to add a button/menu to change the look with a click somewhere on the look ? without opening the menu/pref/look and setting another primary/secondary look and swap ?

haven't tested tk32's look now...

section look_one_presets
int startLayout layouts.standard

// presets section//
section presets
int default_mode  0 // 0 = small, 1 = expanded
int id3_headers  1 //
int smart_tags      1 //
int spectrum      1 // 1 = on
int albumart  0 // 0 = off
int always_on_top  1 //
int small_font  0 //
int minVolume  -40
int albumart_width      70
int albumart_height    this.albumart_width
int time_display      1 // 1 = remaining time, 0 = elapsed time
int use_tracknumber    1 // 1 = use id3 tracknumbers if present, 0 = always use playlistnumber

thx for the tip danz. your look seems a little more cpu intensive (10% usual, jumping up to 40% at times. )

tk32, very low cpu usage (0-5% with both looks, xp2600 here...); just couldn't find the expand button without looking the code (my screen is a little bit too dark...)

thx for the tip danz. your look seems a little more cpu intensive (10% usual, jumping up to 40% at times. )

tk32, very low cpu usage (0-5% with both looks, xp2600 here...); just couldn't find the expand button without looking the code (my screen is a little bit too dark...)

if you want to free up some cpu using the default look, open the ski and edit the following:


section grips
int layer 2
list rect int {0,0,7,7}
// list transcolor color.red
list srcoff int { 392 0 }


you need to add the // to the transcolor line

Hi,

I use the fooAMP skin and have a suggestion.

I like the progress bar in the foobar2000 seek bar since it updates on the fly where you are jumping to, if this same behaviour could be implemented into looks2 (and indeed the fooAMP skin) this would be great.

thanks.

Sorry, i meant the tooltip that comes up that tells you the time currently at the point where you are dragging to, with the current fooAMP design you have to guess where you are dragging to.

also, the albumart isn't transparent as in previous versions, this would be appreciated also.

dynamic tooltips aren't possible yet, sorry


however, i am able to display the jump-to time somewhere else in the skin

Quote

dynamic tooltips aren't possible yet, sorry


however, i am able to display the jump-to time somewhere else in the skin

Hey tk32
How about just having it overtake the current time display.


On another note, great update, but there's one feature I'd like to see: a toggle button for the look to pop up instead of the main GUI.  It's just to difficult having to search through a menu for fewer options than the main interface gives.

I decided to give it a try. No problems
Just one thing - could you change font used in "Overrides" title and section in Preferences to Tahoma?

//Type in skin independent overrides here
section globals
string fontname "Tahoma"

Hey Danz!

I tried use new release foo_looks (2.0 rc1), but on start foobar next text displayed in console

INFO (foo_looks) : Sprite 'background' is visible with empty rectangle
INFO (foo_looks) : Sprite 'albumart' is visible with empty rectangle
INFO (foo_looks) : Sprite 'spectrum' is visible with empty rectangle
INFO (foo_looks) : Sprite 'rolltext' is visible with empty rectangle
ERROR (foo_looks) : malformed number;
  last token read: `0.0' at line 18 in string "..."
ERROR (foo_looks) : Sprite 'seekgrip' Error(s) loading script 'slider'
ERROR (foo_looks) : malformed number;
  last token read: `100.0' at line 5 in string "..."
ERROR (foo_looks) : Sprite 'seekgrip' Error(s) loading script 'seekSliderImpl'
ERROR (foo_looks) : malformed number;
  last token read: `0.0' at line 18 in string "..."
ERROR (foo_looks) : Sprite 'albumartgrip' Error(s) loading script 'slider'
ERROR (foo_looks) : malformed number;
  last token read: `0.0' at line 18 in string "..."
ERROR (foo_looks) : Sprite 'volumegrip' Error(s) loading script 'slider'
ERROR (foo_looks) : malformed number;
  last token read: `100.0' at line 9 in string "..."
ERROR (foo_looks) : Sprite 'volumegrip' Error(s) loading script 'volumeSliderImpl'
INFO (foo_looks) : AssetManager:Dumping unused image 'H:\Audio\Carpenters\(1971) Carpenters\cover.jpg'
INFO (CORE) : opening file for playback :
INFO (CORE) : location: "file://H:\Audio\Carpenters\(1983) Voice Of The Heart\09 - You're Baby Doesn't Love You A.mp3" (0)

I solve this error in next way:

change 0.0 to 0,  100.0 to 100

in  foo_looks_common.ski

Is it correct?

I have W2k russian, foobar 7.7a.

pIv

Quote

Sorry, i meant the tooltip that comes up that tells you the time currently at the point where you are dragging to, with the current fooAMP design you have to guess where you are dragging to.

also, the albumart isn't transparent as in previous versions, this would be appreciated also.

dynamic tooltips aren't possible yet, sorry


however, i am able to display the jump-to time somewhere else in the skin

i'll think about where the best place to show it is.

Hey Danz!

I tried use new release foo_looks (2.0 rc1), but on start foobar next text displayed in console

INFO (foo_looks) : Sprite 'background' is visible with empty rectangle
INFO (foo_looks) : Sprite 'albumart' is visible with empty rectangle
INFO (foo_looks) : Sprite 'spectrum' is visible with empty rectangle
INFO (foo_looks) : Sprite 'rolltext' is visible with empty rectangle
ERROR (foo_looks) : malformed number;
  last token read: `0.0' at line 18 in string "..."
ERROR (foo_looks) : Sprite 'seekgrip' Error(s) loading script 'slider'
ERROR (foo_looks) : malformed number;
  last token read: `100.0' at line 5 in string "..."
ERROR (foo_looks) : Sprite 'seekgrip' Error(s) loading script 'seekSliderImpl'
ERROR (foo_looks) : malformed number;
  last token read: `0.0' at line 18 in string "..."
ERROR (foo_looks) : Sprite 'albumartgrip' Error(s) loading script 'slider'
ERROR (foo_looks) : malformed number;
  last token read: `0.0' at line 18 in string "..."
ERROR (foo_looks) : Sprite 'volumegrip' Error(s) loading script 'slider'
ERROR (foo_looks) : malformed number;
  last token read: `100.0' at line 9 in string "..."
ERROR (foo_looks) : Sprite 'volumegrip' Error(s) loading script 'volumeSliderImpl'
INFO (foo_looks) : AssetManager:Dumping unused image 'H:\Audio\Carpenters\(1971) Carpenters\cover.jpg'
INFO (CORE) : opening file for playback :
INFO (CORE) : location: "file://H:\Audio\Carpenters\(1983) Voice Of The Heart\09 - You're Baby Doesn't Love You A.mp3" (0)

I solve this error in next way:

change 0.0 to 0,  100.0 to 100

in  foo_looks_common.ski

Is it correct?

I have W2k russian, foobar 7.7a.

pIv

lua slider
-- User properties
setlocale("en-us")
trackx = false
...

Next error in new release of foo_looks - 2.0 rc1

If path to the image of album art contained non-english characters  - album cover not displayed.
In my case folder name is russian word.
Previous version - 2.10 work fine.

pIv

Quote

...
On another note, great update, but there's one feature I'd like to see: a toggle button for the look to pop up instead of the main GUI.  It's just to difficult having to search through a menu for fewer options than the main interface gives.

sure

...
as for your other request, i'm not sure i understand what you mean?

can you explain it some more please

Quote

Quote

...
On another note, great update, but there's one feature I'd like to see: a toggle button for the look to pop up instead of the main GUI.  It's just to difficult having to search through a menu for fewer options than the main interface gives.

sure

...
as for your other request, i'm not sure i understand what you mean?

can you explain it some more please

The request was more of one for foo_looks, not your skin.  It was that the look could be accessed by the system tray or taskbar icon instead of the main foobar 2000 gui.


And a small 'bug' I noticed:
If you do not have you look set to always on top and another window moves ontop of it then the look takes on that of the Windows GUI.  Screenshot is below.

(http://members.cox.net/tomatoface/remote/screenupdate.png)

This looks interesting.  Reading documentation now.

Thanks.

lua slider
-- User properties
setlocale("en-us")


lua seekSliderImpl
-- User properties
setlocale("en-us")


lua volumeSliderImpl
-- User properties
setlocale("en-us")

INFO (foo_looks) : Initializing GDI+
INFO (foo_looks) : Sprite 'background' is visible with empty rectangle
INFO (foo_looks) : Sprite 'albumart' is visible with empty rectangle
INFO (foo_looks) : Sprite 'spectrum' is visible with empty rectangle
INFO (foo_looks) : Sprite 'rolltext' is visible with empty rectangle
ERROR (foo_looks) : malformed number;
  last token read: `0.0' at line 19 in string "..."
ERROR (foo_looks) : Sprite 'seekgrip' Error(s) loading script 'slider'
ERROR (foo_looks) : malformed number;
  last token read: `100.0' at line 7 in string "..."
ERROR (foo_looks) : Sprite 'seekgrip' Error(s) loading script 'seekSliderImpl'
ERROR (foo_looks) : malformed number;
  last token read: `0.0' at line 19 in string "..."
ERROR (foo_looks) : Sprite 'albumartgrip' Error(s) loading script 'slider'
ERROR (foo_looks) : malformed number;
  last token read: `0.0' at line 19 in string "..."
ERROR (foo_looks) : Sprite 'volumegrip' Error(s) loading script 'slider'
ERROR (foo_looks) : malformed number;
  last token read: `100.0' at line 12 in string "..."
ERROR (foo_looks) : Sprite 'volumegrip' Error(s) loading script 'volumeSliderImpl'
INFO (CORE) : startup time: 2562 ms
INFO (CORE) : opening file for playback :
INFO (CORE) : location: "file://H:\Audio\Ìèòüêè\Ìèòüêîâñêàÿ òèøèíà\(09) Ìèòüêè - Íà ôåâðàëüñêîì ñíåãó....ogg" (0)
INFO (foo_looks) : AssetManager:Dumping unused image 'E:\Program Files\foobar_0.7\components\foo_looks\looks20.jpg'

2. [..]
I want you to attach a volume controller there like v1.10.
How is it?

Please tell me.

Quote

2. [..]
I want you to attach a volume controller there like v1.10.
How is it?

Please tell me.

There is a volume control on all of the default skin layouts (it isn't obvious though!). If you look just above the album art, you will see a small empty square. If you click and drag this horizontally, you will find it is the volume control..

Hope that helps.

1. I am a Japanese.
A jacket art will not be displayed if Japanese
is contained in the folder name.

Personally, I'd make this layout a bit wider: I find it a bit cluttered up with all those otions in such a small space, but it's the look I use every day cause it doesn't interfere with the other windows.

Ok I know people could get angry. But isn't there a way to make use of WinAmp 3 skin engine somehow? And we'd have access to many skins. WinAmp 3 skins are really beautiful. I am very jealous when I run WinAmp 5, lookwise it kicks fb2k's a**.

Even if it's not possible, could the next version of foo_looks allow FreeForm skinning like WinAmp modern skins? or to achieve such a skinning engine is very hard?

I'm surprised people like to use it on a daily basis as I have almost no graphics skills at all.

- you can make any part of the look appear/move/disappear based on a condition, or a button
for example, you could write a script that swaps the position of the track info & buttons depending on whether the look is docked on the top, or the bottom of the desktop

i'll let you know as i make more progress - i'm planning to have some really innovative features on this skin... watch this space

function onattach(this)
    minx = look_getX(this)
    maxx = look_getWidth(this)
end

tk32: I've noticed a bug in the progress bar code:

Code: [Select]

function onattach(this)
    minx = look_getX(this)
    maxx = look_getWidth(this)
end

I think that minx should be 0, I have a progress bar that is several pixels from left and if I use your code clicks are not properly recognozed, however if I set it to 0 it works just fine. Correct me if I'm wrong.

tk32: I've noticed a bug in the progress bar code:

Code: [Select]

function onattach(this)
    minx = look_getX(this)
    maxx = look_getWidth(this)
end

I think that minx should be 0, I have a progress bar that is several pixels from left and if I use your code clicks are not properly recognozed, however if I set it to 0 it works just fine. Correct me if I'm wrong.

function onattach(this)
    minx = look_getX(this)
    maxx = minx + look_getWidth(this)
end

Quote

Quote

2. [..]
I want you to attach a volume controller there like v1.10.
How is it?

Please tell me.

There is a volume control on all of the default skin layouts (it isn't obvious though!). If you look just above the album art, you will see a small empty square. If you click and drag this horizontally, you will find it is the volume control..

Hope that helps.

You can also use the mousewheel over the background to change the volume.

The volume is positioned the way it is now so it can be visible on all layouts w/o any additional scripting to reposition it.

Quote

1. I am a Japanese.
A jacket art will not be displayed if Japanese
is contained in the folder name.

Fixed in RC2 which I'll post sometime today.

what about the functionality of the dragbar? do you like it?

Quote

what about the functionality of the dragbar? do you like it?

It's great. Thank you =) I appreciate your work.

I hope some day there will be a generic dragbar in the common scripts that will have an option - to use a grip or to use your approach.

I've notived that making simple things requires a lot of code in foo_looks 2.0 if to compare with 1.0. Of course, it's because generic scripts for standard controls are not written yet. My very simple skin is now 700 lines of code, but it was about 100 lines in 1.0.

Right, as I stated, foo_looks 2.0 does less for you but gives you the power and flexibility to do more.  1.x was all about making it easy (thus the large, inefficient graphics layout, the built-in sliders, etc.)

Are you using any of the scripts from foo_look_common.ski?  Those are all intended to be generic and reuseable and to cover common things.  It is far from complete and tk32 and I are both intending to attempt to make as many basic scripts availale as possible so that a basic look can be constsructed by just defining some sprites, importing the common scripts, and attaching those as needed.

I'm even considering expanding the import to allow something like

import http://www.blah.com/commonscripts.ski (http://www.blah.com/commonscripts.ski) and then we could host common scripts on the same site as the looks.

Expect 2.x to continue to improve and remember that in 2.0 I basically started over so its more like a first release then a 2.0 despite the name.

However, there is one thing worth mentioning: when this is loaded, the VM size of foobar increases by about 100kB every second. I noticed this when Windows told me that it had to increase the swap file. After I was aware of that, I tried the foo_looks_one skin. With that loaded the VM size increased by some kilobytes every now and then, mostly when something is animated.

I've toyed around with foo_looks 2.0 and created this thing (http://www.stud.uni-karlsruhe.de/~uzbs/fb2k/endless_tracks.zip), which looks something like this (only the screenshot is not animated):


However, there is one thing worth mentioning: when this is loaded, the VM size of foobar increases by about 100kB every second. I noticed this when Windows told me that it had to increase the swap file. After I was aware of that, I tried the foo_looks_one skin. With that loaded the VM size increased by some kilobytes every now and then, mostly when something is animated.

The most important difference seems to be that my script makes heavy usage of functions that manipulate sprites (change location or image source position).

Yeah, good catch, I had a memory leak in look_setRect().

So are you going somewhere with your tilemap or just messing around - its a cool effect.  I was thinking I might script a space invaders game or something just to show the foo_look sprite manipulations, etc.

just noticed it now, when I try to swap looks from the look components menu, foobar crashes; it does not happen if I use the component menu from the systray.

the slider for album art works great, but it would be nice hiding it in the cover look when the mouse is not on the look for example...

great work !

Also with skins that have playlist windows, will it be possible to alter what the playlist displays so i could have it as artist - track or artist - album - track

also will playlist windows be resizeable like winamp.

the new position of the track and volume sliders obscures the seemingly un-reposistionable total time selected counter, and less importanltly the dB level...

and everytime you restart foobar the small flaoting window interface resets itself to "Standard Mode" ...

really nice work here, i've just started using foo_looks since version 2 appeared and its great.

One thing i'd like to see after playing around with it for a a few hours is the ability to not have to have foo_looks running as always on top. From what  i can see, if you click on foobar in the taskbar it bring up the main foobar window and not the skin. What i'd like is to be able to bring the skin to the front by clicking on the taskbar. I'm not sure if this is possible though. Maybe it would be possible using a toolbar  in a similar way to foo_winbar.

Also with skins that have playlist windows, will it be possible to alter what the playlist displays so i could have it as artist - track or artist - album - track , also will playlist windows be resizeable like winamp.

thanks for any help and keep up the good work

thanks for your efforts teetee

now we just have to wait for danZ to visit the topic and give us some insight


btw, anyone got any foo_looks projects on the go??


---

i added some basic playlist support to my new project

(http://www.btinternet.com/~sean.m.kelly/new_project_ss.png)

hm seems like i'm too stupid to find that playlist  

and is it possible to use circles or other things by specifying multiple points that mark the object's angles? If not, I hereby file that request.
It would make nicer buttons possible. Also, I could perhaps start to design my look

just noticed it now, when I try to swap looks from the look components menu, foobar crashes; it does not happen if I use the component menu from the systray.

the slider for album art works great, but it would be nice hiding it in the cover look when the mouse is not on the look for example...

great work !

you can't declare circular buttons in the, but it can be done!

here's the trick

design the graphics as a PNG file, and place the buttons over an invisible background

only the visible parts of the button will react to mouse movement

so you can design any shape button you like

it's technically called a 'pixel-accurate' hotspot


i'll write a guide when i get time

example to follow......

thanks for the insight, now you mention it i do remember that only the playlist window was resizeable in winamp, and i understand why now.

As for you mentioning having the default ui scaled right down to a playlist this sounds interesting especially if you could have it take on the same look as the controller look.  When i think about it it could be perfect, a very small controller part with a button to bring up a hidden playlist window with multiple playlists.

Also i found a crash, when switching from danz' default look to another look using the component menu built in to the look, it doesn't seem to do it switching from tk32 new look back to danz' default one in the same way:

Yes, if you could strip off the menus, titlebar, etc. and then had the ability to change its appearance (more then what is there now I mean) and the ability to have the two windows working together (moving as one, docking to each other) then you'd have the best of both worlds IMHO.  That's the reason I still don't want to make foo_looks a UI replacement but rather a UI add-on.

Its in essence the setup we have currently we just need a few more hooks to make them really work well together instead of feeling like 2 disjointed items.

INFO (foo_looks) : AssetManager:Dumping unused image 'C:\Programmi\foobar2000\components\foo_looks\looks20.jpg'

you can't declare circular buttons in the code, but it can be done!

here's the trick....

design the graphics as a PNG file, and place the buttons over an invisible background

only the visible parts of the button will react to mouse movement

so you can design any shape button you like

it's technically called a 'pixel-accurate' hotspot


i'll write a guide when i get time

function onrightbuttonup(this)
fb2k_menuCommand("Components/Look/Swap")
end

foo_looks2.0 RC3 doesn't appear to cope with some jpgs with a low number of colours. The file I've uploaded here (http://www.hydrogenaudio.org/forums/index.php?showtopic=17575&view=findpost&p=173529) displays black.

If I then open it in PSP 8.0 and increase the colour depth to 256 colours and resave it, it loads fine.

Thought it might be useful information to know..

we're trying to encourage designers to consider the PNG graphics format as a standard - since it has support for alpha values, and has lossless compression

Quote

we're trying to encourage designers to consider the PNG graphics format as a standard - since it has support for alpha values, and has lossless compression

Oh I agree totally with PNG for the parts of the skin but JPEG is superior (compression-wise) for photographic imagery such as album art (which this image is - I thought I'd mentioned it in my message but obviously not ). Also all websites I've ever seen offering album art to download (saves scanning your own CDs) only have JPEGs and converting JPEG to PNG is a waste of space as it retains all the lossy artifacts and pushed the size up ten-fold..

With starting of Foobar2000 with foo_looks v2.0rc1-rñ3 the screen to the instant becomes black. Such occurs with the change of display resolution in some games or a change of display resolution in the properties of video adapter.
Also the very occurs when I change looks by command looks_swap or change type of standart look (compact to album, etc.).
With use foo_looks of a version of 1.x such it did not occur.
This phenomenon occurs only in Windows XP, in W2K - everything is normal. My video adapter - GeForse 4MX, the version of detonator - any.

foo_looks2.0 RC3 doesn't appear to cope with some jpgs with a low number of colours. The file I've uploaded here (http://www.hydrogenaudio.org/forums/index.php?showtopic=17575&view=findpost&p=173529) displays black.

If I then open it in PSP 8.0 and increase the colour depth to 256 colours and resave it, it loads fine.

Thought it might be useful information to know..

Quote

foo_looks2.0 RC3 doesn't appear to cope with some jpgs with a low number of colours. The file I've uploaded here (http://www.hydrogenaudio.org/forums/index.php?showtopic=17575&view=findpost&p=173529) displays black.

If I then open it in PSP 8.0 and increase the colour depth to 256 colours and resave it, it loads fine.

Thought it might be useful information to know..

I don't do anything special with any image formats, I just pass the filename off to GDI+ and have it load one of its Gdiplus::Image objects.  Maybe MS image codecs don't do well with certain, less common pixel formats.  I don't think I can do much about this w/o writing my own image loaders for the various formats which I don't intend to do.  But thanks for the report so that folks can maybe convert their cover art to at least 8BPP pixel formats.

Quote

Quote

foo_looks2.0 RC3 doesn't appear to cope with some jpgs with a low number of colours. The file I've uploaded here (http://www.hydrogenaudio.org/forums/index.php?showtopic=17575&view=findpost&p=173529) displays black.

If I then open it in PSP 8.0 and increase the colour depth to 256 colours and resave it, it loads fine.

Thought it might be useful information to know..

I don't do anything special with any image formats, I just pass the filename off to GDI+ and have it load one of its Gdiplus::Image objects.  Maybe MS image codecs don't do well with certain, less common pixel formats.  I don't think I can do much about this w/o writing my own image loaders for the various formats which I don't intend to do.  But thanks for the report so that folks can maybe convert their cover art to at least 8BPP pixel formats.

Actually, after thinking about this I'm wrong - I do actually do something to the image when its cover art - I scale it using a scaled blit into a secondary Gdiplus::Bitmap object that has the same pixel format as the source image.  I bet what is happening is that the scaled image doesn't have a palette (index image formats are such a pain in the @ss) so all index lookups return the color black.

The image you posted is reporting itself as 0x00030803 which means it is an 8 bits per pixel index image format.  Did you post the wrong image because you were talking about ones with 4BPP or less.  But this image shows up black too so are you sure you got album art to work that uses 8BPP?

The image you posted is reporting itself as 0x00030803 which means it is an 8 bits per pixel index image format.  Did you post the wrong image because you were talking about ones with 4BPP or less.  But this image shows up black too so are you sure you got album art to work that uses 8BPP?

sprite foobar
string image "bar.png"
bool pixelaccurate true

Failed to load, LUA.DLL not found

*finds it*

WhyTF don't you make this a _REAL_ UI replacement??!
Peter made a great API for custom user interfaces, and yet yuo simply don't use it.

I think most users are still happy with current configuration of fb2k as playlist manager and foo_looks and small, nice looking playback controller.  Correct me if I'm mistaken.

Because I've yet to make or see someone else make a look that can do everything the default UI can do.  foo_looks 2.0 is approaching a point of having enough flexibility to make a  think most users are still happy with current configuration of fb2k as playlist manager and foo_looks and small, nice looking playback controller.  Correct me if I'm mistaken.

I think most users are still happy with current configuration of fb2k as playlist manager and foo_looks and small, nice looking playback controller.  Correct me if I'm mistaken.

i think i can safely say that we can do 'everything' that the main UI can do

it just requires a little specialised scripting

Quote

i think i can safely say that we can do 'everything' that the main UI can do

it just requires a little specialised scripting

Is it possible to display the playlist entries using the Title formatting in the preferences, including the colour codes?

damn you

ok, text & colour is not a strong point at the moment

our text can only be a solid colour, or a two colour gradient

if you want multiple colours, you will need more than one text field to display each item

as for the formatting code, you can cut & paste it into your skin

however, all colour codes will be ignored by foo_looks

as for the formatting code, you can cut & paste it into your skin

format = fb2k_getConfigString("titleformat:Playlist")

Quote

as for the formatting code, you can cut & paste it into your skin

What about adding an interface to config_var_string::g_get_value(), so you can do

Code: [Select]

format = fb2k_getConfigString("titleformat:Playlist")

in a skin?

Quote

I think most users are still happy with current configuration of fb2k as playlist manager and foo_looks and small, nice looking playback controller.  Correct me if I'm mistaken.

Heh, one of the reasons I don't play with foo_looks more is because it doesn't properly replace the GUI. I'd use it occasionally for fun if I could get it to make the main FB2K GUI go away for a little bit. I dislike the inconsistency of having a standard Win GUI window as a playlist and a custom-drawn graphical window as a "control".

You're right that there aren't any looks out there that replace everything, but if the code to do a complete replacement was there, there would be more incentive to make foo_looks a full-yfeatured GUI replacement.

Chicken and egg problem, all over again. Anyhow, add me to the list of people who'd like to see foo_looks hook into the GUI replacement SDK.

Is it possible to hook it in and still retain the "supplemental UI" mode if the user desires?

Quote

damn you

ok, text & colour is not a strong point at the moment

our text can only be a solid colour, or a two colour gradient

if you want multiple colours, you will need more than one text field to display each item

as for the formatting code, you can cut & paste it into your skin

however, all colour codes will be ignored by foo_looks

ok

(sorry to push this more)

Since there isn't a way to measure the width of any particular text (the reason danz can't do only-when-necessary scrolling), wouldn't it be quite hard to reconstruct a playlist with a different colour for Artist, Album, Tracknumber, Title etc. ? You wouldn't know where to place the text fields.. and they'd change with each entry.

Supporting the color codes could be a challenge.  The only way I can think to do it is to parse every string that gets rendered and resetting the current pen every time I encounter a color code block.  Sounds like a pain.  I'd be curious to know how PP handles this in the default UI since he must be ownerdrawing the list control for the playlist entries.

Quote

Supporting the color codes could be a challenge.  The only way I can think to do it is to parse every string that gets rendered and resetting the current pen every time I encounter a color code block.  Sounds like a pain.  I'd be curious to know how PP handles this in the default UI since he must be ownerdrawing the list control for the playlist entries.

Presumably he uses uTextOutColors (or rather uTextOutColorsTabbed) from utf8api.dll. Source code is included in the SDK, so you can see how it's done.

look_setFspec(sprite,fb2k_getConfigString('titleformat:Playlist'))

Unless I misunderstand those he must be parsing the source string somewhere else to create multiple calls to uTextOuColors with the appropriate substring and color.  That's what I was saying I'd have to do - parse each string and break out each chunk that is a particular color then set the pen, render, then get next chunk on through.  I can't use these functions since my rendering is all custom and uses GDI+ for text rendering.

Quote

Unless I misunderstand those he must be parsing the source string somewhere else to create multiple calls to uTextOuColors with the appropriate substring and color.  That's what I was saying I'd have to do - parse each string and break out each chunk that is a particular color then set the pen, render, then get next chunk on through.  I can't use these functions since my rendering is all custom and uses GDI+ for text rendering.

uTextOutColors calls text_out_colors, which does parse color codes. The passed color is the default color as set in preferences.

if anyone would like to play with my new skin project, you can get it here:

download here. (http://www.btinternet.com/~sean.m.kelly/tk32-new_skin_project.zip)


i've tried to organise the code in a very user-friendly way.

there are no core scripts used, i have written my own


i import the scripts from new_project_common.ski


i am currently working on the playlist mode, so it's still pretty buggy.

any suggestions are appreciated

sprite foobar
list rect int { 0,0,400,15 }
list srcoff int { 20,20 }
list tilesize int { 10, 15 }

how can i avoid this:
(http://home.arcor.de/jpichler/extern/foo_looks.jpg)

Quote

how can i avoid this:
(http://home.arcor.de/jpichler/extern/foo_looks.jpg)

by keeping the look in always-on-top mode

or by moving the mouse over the look

please tell me what you did in order to produce this display

i think i can safely say that we can do 'everything' that the main UI can do

it just requires a little specialised scripting

tk32: It's strange, but your new look isn't visible here (WinXP SP1). I just downloaded it, but nothing shows up when I activate it. Any ideas? DanZ's default look works as it should though.

Sorry, I was stupid and I'll go hide now...      
I tried to activate new_project_common.ski 

Sorry, I was stupid and I'll go hide now...      
I tried to activate new_project_common.ski 

Btw: Is the small "now playing marker" supposed to follow when scrolling the playlist? Is it indended to indicate the direction of the current track or something.

Quote

Btw: Is the small "now playing marker" supposed to follow when scrolling the playlist? Is it indended to indicate the direction of the current track or something.

it's supposed to show the current track

but it's not working yet

i'm working on it now

---

btw danZ, i think we need to have an extension that indicates that it will be used for lua scripts only

i was naughty to place some section declarations in mine as well. i will move them to the ski now

.lua is cool i think

is it possible for the standard look of foo_looks 2.0 RC to remember its layout?

Quote

how can i avoid this:
(http://home.arcor.de/jpichler/extern/foo_looks.jpg)

by keeping the look in always-on-top mode

or by moving the mouse over the look

please tell me what you did in order to produce this display

I've done a test of the standard Foo_looks under WIN 98 SE, these are the results

Quote

Quote

how can i avoid this:
(http://home.arcor.de/jpichler/extern/foo_looks.jpg)

by keeping the look in always-on-top mode

or by moving the mouse over the look

please tell me what you did in order to produce this display

Maybe its that strange "feature" I've heard about EndPaint... If something invalidates a region of your window while you're still repainting it (between BeginPaint and EndPaint) the whole window region will still be validated by the EndPaint call. Does anyone know a better solution than avoiding BeginPaint/EndPaint?

sprite foo
string image "bar.png"
list rect int { 0,0,200,5}
list tilesize int {5,5}

fb2k_getConfigString(name)

function onattach(this)
    look_setFspec(this,fb2k_getConfigString('titleformat:Playlist'))
end

i spent the last few days thinking about how to achieve this feature without tiling


now i'll add it to my project skin in the form of a resizable corner handle

I am using RC4 (I think) - http://www.loodi.com/foo_looks_beta.zip (http://www.loodi.com/foo_looks_beta.zip), right?

thanks tk32, that's just what i needed

i'm also using the dynamic title formatting from upnorth, for the record..

edit: errrr.. apparently that wasn't what i needed.. same error 

EDIT:
if you are still getting errors after downgrading, you may need to delete these DLL's from the foo_looks folder:

luaCOMExtension.dll
luaRegexExtension.dll

this is just a speculation - but they might be responsible for the errors
(since they were not present in the RC4 install)

luaCOMExtension.dll
luaRegexExtension.dll

that's unfortunate

ok, here's the deal until danZ can answer:


unless you are a look designer - stick to RC4 for the time being



in RC4, foo_looks didn't try to interface with the title-formatting at all

i will inform danZ of the potential title-formatting bug

function onattach(this)
    look_setFspec(this,fb2k_getConfigString('titleformat:Playlist'))
end

function onattach(this)
look_setFspec(this,fb2k_getConfigString('titleformat:Playlist'))
end

Danz,

I ask you again.

If Foobar200 started minimized to tray and then I activate looks - change volume level with mouse wheel unavailable, I must activate main windows of Foobar and point mouse to looks again. Only in this case I must change volume level with mouse wheel.
Is this a bug or peculiarity of looks.

100.0 / 3.0
= 33.33333333333334

100 / 3
= 33.33333333333334

My seconf question: in foo_looks_common.ski and another available fo me skins I change real 100.0 to integer 100 and 0.02  to 1/50 (regional setting in lua not work).  I not found any errors, when I made this changes. It is correct?

Danz,

I ask you again.

If Foobar200 started minimized to tray and then I activate looks - change volume level with mouse wheel unavailable, I must activate main windows of Foobar and point mouse to looks again. Only in this case I must change volume level with mouse wheel.
Is this a bug or peculiarity of looks.

My seconf question: in foo_looks_common.ski and another available fo me skins I change real 100.0 to integer 100 and 0.02  to 1/50 (regional setting in lua not work).  I not found any errors, when I made this changes. It is correct?

Quote

My seconf question: in foo_looks_common.ski and another available fo me skins I change real 100.0 to integer 100 and 0.02  to 1/50 (regional setting in lua not work).  I not found any errors, when I made this changes. It is correct?

This is a 'feature' of Lua. The Lua parser accepts floating point numbers in the same format as used in virtually any other programming language (basically the English format). However, to convert a string to the actual floating point value that is then used in Lua, it uses the strtod function from the C library which is locale-dependent.
For my foo_lua project, I patched Lua to use a custom version of lua_str2number, which is by default #defined as str2d in lobject.c.

Lua supports only one number type natively. By default this is set to 64 bit floating point. If you need integer division, use floor(a/b) (for a positive quotient), or ceil(a/b) (for a negative quotient), to get the same results as with integer division.

Foo_looks seems to be doing something weird with certain title formatting strings - http://pelit.koillismaa.fi/fb2k/strings.php?f=40 (http://pelit.koillismaa.fi/fb2k/strings.php?f=40) gives a syntax error and eats up all your CPU time.

Any idea why

setlocale()

won't work?

That is, every script that was going to rely on floating point contants, etc. could call this before doing any floating point operations.

I tried this locally, in that I set the local to Russian and the lua parser then correctly gave me errors for 100.0, etc. when I ran my look.  But when I instructed the Russian user to use setlocale("en-us") it did not correctly handle the 100.0, etc.

• pop-up button panels (for playback/playlist controls)
• support for resizing the skin
• replace the scroll up/down buttons in PL view with a custom scrollbar

i was considering:

• pop-up button panels (for playback/playlist controls)
  
• support for resizing the skin
  
• replace the scroll up/down buttons in PL view with a custom scrollbar

suggestions please

sprite spectrum
list rect int { 9 42 220 40 }
list srcoff int { 290 85 }
int bands 20
list rendermap int {}
list scripts string { "spectrumAnim" }

Quote

suggestions please

About the mini mode:

- make its height equal to window titlebar
- add (if not already there) a clickable progress bar of the current song (perhaps on mouseover?)
- place one button to close the look and one button to close fb2k (but don't ask me how to graphically differentiate them  )
- make artist - title scroll when there's not enough space to fully display those info

HTH.

Alessandro

how many rc's will foo_looks 2.0 go thru before its public, also is 2.0 compatible with 1.0 skins?

Quote

Quote

I think most users are still happy with current configuration of fb2k as playlist manager and foo_looks and small, nice looking playback controller.  Correct me if I'm mistaken.

Heh, one of the reasons I don't play with foo_looks more is because it doesn't properly replace the GUI. I'd use it occasionally for fun if I could get it to make the main FB2K GUI go away for a little bit. I dislike the inconsistency of having a standard Win GUI window as a playlist and a custom-drawn graphical window as a "control".

You're right that there aren't any looks out there that replace everything, but if the code to do a complete replacement was there, there would be more incentive to make foo_looks a full-yfeatured GUI replacement.

Chicken and egg problem, all over again. Anyhow, add me to the list of people who'd like to see foo_looks hook into the GUI replacement SDK.

Is it possible to hook it in and still retain the "supplemental UI" mode if the user desires?

Thanks for your point of view.  I'll see if there is a clean and simple way to support both modes (UI addon and UI replacement).

• the basic skin graphics guidelines are here (http://www.hydrogenaudio.org/forums/index.php?showtopic=16500&view=findpost&p=164147)
• the beginners coding tutorial is here (http://www.btinternet.com/%7esean.m.kelly/foo_looks/tutorial.htm)
• the additional coding tutorials (text only) are here: #001 (http://www.btinternet.com/~sean.m.kelly/how-to_guide_001.txt) & #002 (http://www.btinternet.com/~sean.m.kelly/how-to_guide_002.txt)

2.0 will be released very soon

we are in the very final stages of testing RC6, and just waiting for my lazy a$$ to finish my new skin so that it can be released in conjunction with it.

my guess is about 4 days


btw: is anyone out there working on any skins / graphics for the plugin?

we'd love some contributions .. in any form

if it's lack of support, or knowledge, then please don't hesitate to let me know. i'm happy to write as many tutorials as it takes for you all to be comfortable with the process.

and if you're worried about coding, then just show me your Photoshop/PSP skills and let me do the rest for you.

• the basic skin graphics guidelines are here (http://www.hydrogenaudio.org/forums/index.php?showtopic=16500&view=findpost&p=164147)
  
• the beginners coding tutorial is here (http://www.btinternet.com/%7esean.m.kelly/foo_looks/tutorial.htm)
  
• the additional coding tutorials (text only) are here: #001 (http://www.btinternet.com/~sean.m.kelly/how-to_guide_001.txt) & #002 (http://www.btinternet.com/~sean.m.kelly/how-to_guide_002.txt)

i am looking for suggestions on what to write for tutorial guide #003

please support us and make a contribution[/i]

()

Will it be updated for the 0.8 SDK by RC7?

Is it still so that the alpha blending support is only for different layers of the skin?

weee.... got my own skin in progress, but it will take some time to get it done.
little preview:

Quote

Is it still so that the alpha blending support is only for different layers of the skin?

You can alpha blend the whole window with the desktop at a constant value

section window
int alphablend [0-100]

sprites can be individually blended with the sprites under them using same syntax

sprite foobar
int alphablend [0-100]

Quote

Quote

Is it still so that the alpha blending support is only for different layers of the skin?

You can alpha blend the whole window with the desktop at a constant value

section window
int alphablend [0-100]

sprites can be individually blended with the sprites under them using same syntax

sprite foobar
int alphablend [0-100]

Yes I know that, but what I meant was is there a way to get nice freeform skins (ie a circle) with antialiased edges?

Ok thanks for clearing that up. I believe that if (when) you get it implemeted we'll see a huge amount of new cool looks

INFO (foo_looks) : Sprite 'progBar' is visible with empty rectangle
INFO (foo_looks) : Sprite 'progBar2' is visible with empty rectangle
INFO (foo_looks) : Sprite 'nowPlaying' is visible with empty rectangle
ERROR (foo_looks) : attempt to call global `look_measureTextAbs' (a nil value)
ERROR (foo_looks) : attempt to call global `look_measureTextAbs' (a nil value)
ERROR (foo_looks) : attempt to call global `look_measureTextAbs' (a nil value)

Hey, tk32

Code: [Select]

INFO (foo_looks) : Sprite 'progBar' is visible with empty rectangle
INFO (foo_looks) : Sprite 'progBar2' is visible with empty rectangle
INFO (foo_looks) : Sprite 'nowPlaying' is visible with empty rectangle
ERROR (foo_looks) : attempt to call global `look_measureTextAbs' (a nil value)
ERROR (foo_looks) : attempt to call global `look_measureTextAbs' (a nil value)
ERROR (foo_looks) : attempt to call global `look_measureTextAbs' (a nil value)

Yeah, seems to be working fine after changing tracks a few times using the buttons in the look. Looks really good btw, excellent work

Quote

But it is not good idea start scrolling only by pressure of buttons in the look.

When I start Foobar again - I an not scrolling text.

As BUSH wrote

Quote

Yeah, seems to be working fine after changing tracks a few times using the buttons in the look. Looks really good btw, excellent work

But it is not good idea start scrolling only by pressure of buttons in the look.

When I start Foobar again - I an not scrolling text.

[[span style='font-size:11pt;line-height:100%']**conditions apply. you may be required to make a premium rate toll call to receive your gift.[/span]

that's cool

it's fair game.

i'm just glad you realised it was a joke
-------------------------

Could you also post a compile with 0.8 SDK ? Thanks.

To tk32

Your look micropanel is fine, but:

1. Not work - activate main windows by rightmouseclick on "PL"

2. Show console by leftmouseclick on "C" not work also.

In skin fooAMP2 volume changed by mouse wheel, but volume slider not moved in this case. Main windows in fooAMP2 not activated also.

The bug with activation main windows is absent in foo_looks_beta2.0rcX

• right clicking PL works
• the 'c' console button works

in fact, the vertical white bar was reserved for that very reason

the bug must be on your machine only

Quote

To tk32

Your look micropanel is fine, but:

1. Not work - activate main windows by rightmouseclick on "PL"

2. Show console by leftmouseclick on "C" not work also.

In skin fooAMP2 volume changed by mouse wheel, but volume slider not moved in this case. Main windows in fooAMP2 not activated also.

The bug with activation main windows is absent in foo_looks_beta2.0rcX

i don't understand

the bug must be on your machine only

• right clicking PL works
  
  
• the 'c' console button works

as for fooAMP2 - the mouse wheel update is a real bug, so thanks. i will fix it

as for the other thing about main windows - i don't understand


could you try to explain it for me

sorry

---
bernard,

you're right - i have omitted a volume control from micropanel - but i can easily add one

in fact, the vertical white bar was reserved for that very reason

to be honest - i wanted to know how important it was for people to have one.

i will have an update by the end of the day

here it is...
foo_looks 2.0 (http://www.loodi.com/foo_looks.zip)

Just started experimenting with foo_looks 2.0 and would appreciate an answer to a question I have:

I am attempting to load and display album art at its native aspect ratio, but am having trouble getting the image size (in pixels) of an image loaded using look_loadImage().

I've looked at http://www.btinternet.com/~sean.m.kelly/functions_list.txt (http://www.btinternet.com/~sean.m.kelly/functions_list.txt) but have not been able to find a related function.

To tk32

This bug with rightclick on "PL" an leftclick on "C"  I  hav only with version foobar 0.8b5.
I  install foobar 0.77b again and all is OK!

I change in looks string to "PL" button

fb2k_menuCommand('Foobar2000/Activate main window')

to string

fb2k_menuCommand('Foobar2000/Exit').

That work in both versions of Foobar.

Also command: fb2k_menuCommand('Components/Show console') not work with Foobar 0.8b5.

Quote

I am attempting to load and display album art at its native aspect ratio, but am having trouble getting the image size (in pixels) of an image loaded using look_loadImage().

I don't have functions for any manipulations or information on images except for loading
[snipped]
I can add the ones you suggested for next release.

First concept done 

Illegal operation:
Code: C0000005h, flags: 00000000h, address: 013CFEECh
Access violation, operation: read, address: FFFFFFFFh
Call path:
WinMain=>app_shutdown
This is the first crash logged by this instance.
Code bytes (013CFEECh):
013CFEACh:  90 90 90 90 8B C1 33 C9 89 08 89 48 04 89 48 08
013CFEBCh:  89 48 0C 89 48 10 89 48 14 89 48 18 89 48 1C C3
013CFECCh:  90 90 90 90 8B C1 33 C9 89 48 04 89 48 18 C3 90
013CFEDCh:  90 90 90 90 83 EC 2C 53 8B 1D 44 2D 3F 01 56 57
013CFEECh:  8B 43 04 50 68 20 2F 3F 01 E8 B6 25 FE FF B9 0B
013CFEFCh:  00 00 00 BE 30 2F 3F 01 8D 7C 24 14 83 C4 08 F3
013CFF0Ch:  A5 8B 4B 04 51 FF 15 20 63 3E 01 F7 D8 1B C0 B9
013CFF1Ch:  0B 00 00 00 F7 D8 8D 74 24 0C BF 30 2F 3F 01 89
Stack (0067FD1Ch):
0067FCFCh:  0000017F 00210216 0067FD1C 00000187
0067FD0Ch:  BFF55769 100036BA 00000000 00000024
0067FD1Ch:  BFF55769 100036BA 00000000 013D6F51
0067FD2Ch:  013F2A78 013D077C 100036BA 004011A0
0067FD3Ch:  0043189D 0067FD70 00000009 004318E0
0067FD4Ch:  0067FD70 00000009 00411211 00000000
0067FD5Ch:  8162C3A2 00000000 00000720 00000113
0067FD6Ch:  0000000A 113773C4 4B48B387 58ABDF8B
0067FD7Ch:  38E56CBC 00000007 000002D0 013F2A70
0067FD8Ch:  0067FD9C 0040FF0E 00000000 00000000
0067FD9Ch:  0067FE38 004367E5 00400000 00000000
0067FDACh:  8162C3A2 00000001 00000000 81618D50
0067FDBCh:  00570000 C0000005 8162C3A2 007A09E0
0067FDCCh:  00000000 00000000 007A0BC0 00000001
0067FDDCh:  00000044 00000000 00000000 00000000
0067FDECh:  00000000 00000000 00000000 00000000
0067FDFCh:  00000000 00000000 00000000 00000401
0067FE0Ch:  00000001 00000000 00000000 000011A2
0067FE1Ch:  00000000 0067FDB4 0067FB4C 0067FF68
0067FE2Ch:  00436810 00439CA8 00000000 0067FF78
Registers:
EAX: 013E6E98, EBX: 00000000, ECX: 013F2A70, EDX: 0000000A
ESI: 100036BA, EDI: BFF55769, EBP: 0067FD8C, ESP: 0067FD1C
Failed to get module/symbol info.

Version info:
foobar2000 v0.8 beta 2
ANSI

Quote

First concept done 

Are you going to need help with the scripting?

then danZ & myself will help you with some nice custom scripts

Also, looking at the skin.jpg graphic - is there a way in photoshop or whatever to save the image with the alpha values around the edge intact rather then having it antialiased to the transparent background color?  ie. so that the edges would instead blend with the desktop instead getting the blackish jaggies as in the current version.

this has been discussed before

unfortunately we are not able to support win98

sorry

(am I really the only win98 user?  maybe there are some download stats from before the builds were unified)

list rendermap int { render.Erase render.image }

bool pixelaccurate true

sprite button_play
list rect int { 35 20 70 71 }

w00t
basic scriptingstuff done.
I've just got to think about the design of the tags etc.
Now it's going towards the creepy stuff  

http://home.arcor.de/theurmel/skin_raw.png (http://home.arcor.de/theurmel/skin_raw.png)
http://home.arcor.de/theurmel/skin_raw.ski (http://home.arcor.de/theurmel/skin_raw.ski)

sprite text_title_head
list rect int { 115 30 40 20 }
int fontsize 7
string text "title:"

if fb2k_isPlaying() then fb2k_playPause() else fb2k_playStart() end

thx guys
fixed most of the problems I noticed. The cropped playbutton gave me a lot of (useless work). I moved some buttons around, recreated the image the 1000th time etc. without checking the scriptcode  

The playback script is a (most likeley everlasting) hack to get the skin usable, I played around with the functions themselfes as described in your guide, but that produced a long list of functions, and I wanted to know how to do this thing:

Code: [Select]

if fb2k_isPlaying() then fb2k_playPause() else fb2k_playStart() end

So I looked at your new_project.ski and copied the whole script because it looked much more elegant than my solution 

Also it's a technique I also used for some eMule-Modifications. Advanced Copy&Pasting. Take other code, understand what it is doing and use it for your own purposes.

The things I gonna need help with:
1. The Seekbar

import foo_looks_common.ski

sprite seekgrip
list scripts string { "slider[minx=5 maxx=102 trackx=true]","seekSliderImpl" }

• beginners tutorial (http://www.btinternet.com/%7esean.m.kelly/foo_looks/tutorial.htm)
• how-to guide #001 (http://www.btinternet.com/%7esean.m.kelly/how-to_guide_001.txt)
• how-to guide #002 (http://www.btinternet.com/%7esean.m.kelly/how-to_guide_002.txt)

so far we only have 3 fully working skins

default
fooAMP
micropanel

really nice looking skin aero..  but it doesn't seem to work too well with foobar 0.8b6.. the seek bar and volume slider are locked in the far left positions.. the playback and volume are unaffected by clicking on them.. same with the balance slider... the playlist button doesn't bring up the playlist (i think that's addressed earlier in this thread though..) also the toggles on the time display screen are invisible until they're selected, so it takes a few misclicks to get it just right..  i don't know if that's because there's no highlight-on-rollover implented in the skin or if there is and it's just not working..

when you say this skin allows the porting of wa2 skins, you mean i can use other skins besides the one you've included? how would i go about doing that?

tk32:

i read the robouk photoshop tutorial on creating an mp3 player interface and i've made a base similar to the one in the tutorial.. i'm going to try to make some buttons for it, but i don't think i'll be able to handle the coding.. would you be able to help me out on that front?

thanks
bogs

section window
int width 270 
int height 155

sprite background
list rect int { 0 0 window.width window.height }

sprite prev_button
list rect int { 30 78 65 34 }
list srcoff int { 0 124 }

sprite play_button
list rect int { 34 22 70 71 }
list srcoff int { 68 124 }

sprite next_button
list rect int { 30 2 65 34 }
list srcoff int { 230 124 }

sprite stop_button
list rect int { 78 45 27 26 }
list srcoff int { 203 123 }

To Danz

1. I tried your foo_looks 2.1beta1 with foobar 0.8b6.

Activate playlist and show console commands in look now work, but  look command "Exit Foobar" (pressing button) crashed Foobar.
When I select this command from another location (tray or menu) all OK.

hand_orb.png (http://www.btinternet.com/~sean.m.kelly/hand_orb.png)
hand_orb.ski (http://www.btinternet.com/~sean.m.kelly/hand_orb.ski)

I only did a quick test with 0.8 to see if foo_looks loaded OK and it did.  It appears there are some SDK changes that are affecting certain aspects of the looks.

Quote

I only did a quick test with 0.8 to see if foo_looks loaded OK and it did.  It appears there are some SDK changes that are affecting certain aspects of the looks.

Could you please elaborate? I'm about to start playing with foo looks again, but if it can't be used with v.0.8 beta x-xx and the future RC x then I might wait and improve my graphics skills instead.

I understand your decision to wait for a final release, but the fact that previous versions have had maybe 30 betas and 10 RC's, we might be talking about quite some time before we see a final release. I suppose quite a few people use betas because if they didn't there wouldn't be any serious beta testing either.

IIRC this has happend before, foo_WSGUI/foo_looks waiting for a final release of foobar2000, but as a plugin for a player that is under (heavy) development itself, your decision doesn't really encourage people to develop all the looks tk32 and yourself seems to hope for. It's lagging one step behind and making it hard for itself to be recognised as a good and useful plugin.

I'm looking forward to start fiddling with my own look, but it's hard to learn when you don't know if the bug is because of something you did yourself, or because the plugin isn't compatible with the most recent version of foobar2000. That kind of thing tends to make me lose my motivation. I've also got the impression that not alot has changed in the SDK, and that most plugins compiled for v.0.7 would also work with v.0.8beta. If that is true and I isn't too much work I'm hoping for an update of foo_looks that doesn't have any serious issues (if there is any at the moment) with the betas.

But, don't get me wrong, I really appreciate all the work you have done and still do to make this plugin something special!


tk32: I really appreciate the links to those graphics tutorials, and also all the work you do to make it easier to get started. Thanks! 

v2.1 Beta 2 with tk32's "hand_orb" is just amazing. I don't think I have seen such perfectly round edges ever before. Doesn't use "any" CPU when dragged around all over my screen either. Truly great work! 

Quote

I only did a quick test with 0.8 to see if foo_looks loaded OK and it did.  It appears there are some SDK changes that are affecting certain aspects of the looks.

Could you please elaborate? I'm about to start playing with foo looks again, but if it can't be used with v.0.8 beta x-xx and the future RC x then I might wait and improve my graphics skills instead.

I'm looking forward to start fiddling with my own look, but it's hard to learn when you don't know if the bug is because of something you did yourself, or because the plugin isn't compatible with the most recent version of foobar2000. That kind of thing tends to make me lose my motivation. I've also got the impression that not alot has changed in the SDK, and that most plugins compiled for v.0.7 would also work with v.0.8beta. If that is true and I isn't too much work I'm hoping for an update of foo_looks that doesn't have any serious issues (if there is any at the moment) with the betas.

• hand_orb.png (http://www.btinternet.com/~sean.m.kelly/hand_orb.png)
• hand_orb.ski (http://www.btinternet.com/~sean.m.kelly/hand_orb.ski)

sprite slider_volume
int layer 1
list rect int { 21 26 20 0 } 
list srcoff int { 170 195 }

sprite volume_box
string include slider_volume
int height 62
list rendermap int { }
list scripts string { "urmel_vol_drag[bar=slider_volume]" }

Quote

Quote

I only did a quick test with 0.8 to see if foo_looks loaded OK and it did.  It appears there are some SDK changes that are affecting certain aspects of the looks.

Could you please elaborate? I'm about to start playing with foo looks again, but if it can't be used with v.0.8 beta x-xx and the future RC x then I might wait and improve my graphics skills instead.

I'm looking forward to start fiddling with my own look, but it's hard to learn when you don't know if the bug is because of something you did yourself, or because the plugin isn't compatible with the most recent version of foobar2000. That kind of thing tends to make me lose my motivation. I've also got the impression that not alot has changed in the SDK, and that most plugins compiled for v.0.7 would also work with v.0.8beta. If that is true and I isn't too much work I'm hoping for an update of foo_looks that doesn't have any serious issues (if there is any at the moment) with the betas.

The only real problem is that menu entry strings changed a lot between 0.7 and 0.8, so anything where you assign a button in foo_looks to call a menu command like:
fb2k_menuCommand("Foobar2000/Hide main window")
in 0.8 the command is now
fb2k_menuCommand("Foobar2000/Activate or hide main window")


See back a few pages of discussion for some more changed entries.:
http://www.hydrogenaudio.org/show.php/showtopic/17279/st/225 (http://www.hydrogenaudio.org/show.php/showtopic/17279/st/225)

So when we will have final release?

and when the homepage will be updated ?

And hey we need more skins 

The API was extended in 0.8 beta 5 so that menu actions can also have GUIDs, and thus can be invoked by GUID. All of the core menu actions now have GUIDs, declared in guid.h.

... Of course, this now means that for any components to take advantage of this feature, they have to be extended to support it. Gee, how would this system be supported in a script? Hardcoded GUIDs, or functions which support GUID parameters and an includes file with the standard GUID set? Or is it even worth implementing?

core_menus = { foobar2000=GUIDforfoobar2000, etc }

then in scripts you could do

fb2k_mainMenu(core_menus.foobar2000)

1) Is it possible to somehow get the look work like this: normally it would show only the orb part with now playing info etc, but when a button is clicked, the playlist part would somehow "slide" out? And of course a new click would make it slide back again?

3) tk32: hope you don't mind that I stole the visualization from the last look you posted. Or actually just the idea and the graphic, haven't had time to do anything else than the graphics for the look.

What I'm working on:

Quote

What I'm working on:

I have a question, how are the track ratings done stored  - meta data, another third party component, ???  While what you show graphically with the stars is easily doable I'm just wondering where the actual data comes from to decide how many stars to render.

look_setToggle(this, not look_getToggle(this))

Yes it's just a custom tag just as tk32 said. I'm actually breaking standards and use a scale of 1 to 6

Yes it's just a custom tag just as tk32 said. I'm actually breaking standards and use a scale of 1 to 6

Gah LUA is shite. In LUA, 0 is true, so I can't even do something simple like:

Code: [Select]

look_setToggle(this, not look_getToggle(this))

Maybe you could change the return types of setToggle and getToggle to booleans, danZ?

if look_getToggle(this) == 1 then 
    look_setToggle(this, 0) 
else
    look_setToggle(this, 1)
end

Gah LUA is shite. In LUA, 0 is true, so I can't even do something simple like:

Code: [Select]

look_setToggle(this, not look_getToggle(this))

Maybe you could change the return types of setToggle and getToggle to booleans, danZ?

    if (look_getToggle(this) == 0) then
  look_setToggle(this, 1)
    else
  look_setToggle(this, 0)
    end

function onleftbuttonup(this)
      if look_getToggle(this) == 1 then
         look_setToggle(this, 0)
      else
         look_setToggle(this, 1)
      end
   end

it would break all our current skins to change the return type of the current functions

Why don't we make sure we get the API right from the start, this time around?

Just a few more questions:

So, if I want to get the visualization alpha blended like in tk32's hand_orb do I have to do it like tk32 has done? With a new layer that goes on top of the visualization and has an alpha blended border?

Also about the stars. Is it enough if I put just one star to the .png? I mean, can I (we) use it for both, the opaque and the semi-transparent stars? I believe it's possible, but I'm just checking

More questions will follow

Thanks for the quick response and good work, danZ - Looking forward to it.

Quote

Just a few more questions:

So, if I want to get the visualization alpha blended like in tk32's hand_orb do I have to do it like tk32 has done? With a new layer that goes on top of the visualization and has an alpha blended border?

Also about the stars. Is it enough if I put just one star to the .png? I mean, can I (we) use it for both, the opaque and the semi-transparent stars? I believe it's possible, but I'm just checking

More questions will follow

the spectrum bar graphic can have its own alpha values to blend it with the background but to contrain it to the oval you'll need some type of overlay mask - tk32 can eloborate.

for the stars the easiest way to do it would be to render a graphic with all 6 stars "on" and have the background contain all 6 stars "off".

The look would then use one sprite for the "on" stars at a higher layer and would use the rating to determine the width of the sprite thus clipping it to render ony X on stars.

That's quite much how I was thinking of doing it when I started designing the look, but some people who use a scale of 1-5 might not like it
Oh well, I'll just do what you suggested.

lua togglefb2k
   function onleftbuttonup(this)
      if fb2k_uiIsActivated() then
         fb2k_menuCommand("Foobar2000/Hide main window")
         look_setToggle(this, 0)
      else
         fb2k_menuCommand("Foobar2000/Activate main window")
         look_setToggle(this, 1)
      end
   end
endlua

hi anza

the only way to get a faded edge on spectrum & text fields is to use a graphical mask

it's even essential when it comes to textscroll (although i am thinking about how to code i universal textscroll that doesn't require a mask)


if you don't feel confident creating the mask graphic, i can help out


as for the stars, you'll only need to draw (in photoshop) 1 on, and 1 off

code can do the rest

b nice if somebody redid the coal skin, in my opinon thats the best toolbar like skin

What would be the fastest way of doing a good mask? Would just a plain "copy the orb and use feather tool to get rid of the center" work well or is there some secret way of doing über cool fades?

Quote

b nice if somebody redid the coal skin, in my opinon thats the best toolbar like skin

If you talk about this one:

"string fspec "%guess_artist.artist% - %guess_title.title%"

tk32, ok thanks for the "tutorial"  I'll try it later.

I just can't figure out what kind of buttons would be good for the look.. Perhaps something like this?

@Anyone:  
I can't figure out how to concatenate strings. I'm trying to use the guessing code from my "dynamic" playlist formatting, and that works like it should, but how do I concatenate the guessed artist and title info into one single fspec for display?

Here is an example, but I have tried quite a few things:

Code: [Select]

"string fspec "%guess_artist.artist% - %guess_title.title%"

Hopefully you get the idea. "guess_artist" and "guess_title" are sections and "artist" and "title" are strings (obvious I guess).

sprite album
list fontcolor int { 170 0 0 0 }
list rect int { 12 82 207 11 }
int fontsize 7
string fspec $if(%tracknumber%,#$num(%tracknumber%,2) - )$upper(%album%) $if3('('%year%')','('%date%')')

Another (stupid) question:

Code: [Select]

sprite album
list fontcolor int { 170 0 0 0 }
list rect int { 12 82 207 11 }
int fontsize 7
string fspec $if(%tracknumber%,#$num(%tracknumber%,2) - )$upper(%album%) $if3('('%year%')','('%date%')')

After putting that to my .ski I get this error:

INFO (foo_looks) : Look file 'D:\Applications\foobar2000\components\foo_looks\orb.ski' modified - Reloading
ERROR (foo_looks) : Failed to load 'D:\Applications\foobar2000\components\foo_looks\orb.ski'
ERROR (foo_looks) : [Error] [Line: 47] Token = '#$num(%tracknumber%'
ERROR (foo_looks) : [Error] [Line: 48] Token = ')$upper(%album%)'

What's wrong?

edit:

changing the string to


string fspec #%tracknumber%-$upper(%album%)'('%date%')'

makes it work but it's not what I want...

section presets
int minvolume -45

lua volumebar
   min = look_getValue(presets, minvolume)

   function updateBar(this)
       ...
   end

   function onvolumechange(this, newvol)
      updateBar(this)
   end
endlua

ERROR (foo_looks) : attempt to perform arithmetic on global `min' (a nil value)

I'm making a volume bar by using the following code - Removed some stuff:

Code: [Select]

section presets
int minvolume -45

lua volumebar
   min = look_getValue(presets, minvolume)

   function updateBar(this)
       ...
   end

   function onvolumechange(this, newvol)
      updateBar(this)
   end
endlua

However, I get the following message, because look_getValue isn't returning anything:

Quote

ERROR (foo_looks) : attempt to perform arithmetic on global `min' (a nil value)

It works fine, when I enter a value instead of the look_getValue, so what am I doing wrong?

section trackinfo
int layer 2

sprite artist
string include trackinfo
list rect int { 10 1 230 16 }
int fontsize 8
string fspec "%tagz._Artist-Title%"

I'm stuck  

How can I make this text disappear on mouseover, to reveal my playback buttons underneath?

Code: [Select]

section trackinfo
int layer 2

sprite artist
string include trackinfo
list rect int { 10 1 230 16 }
int fontsize 8
string fspec "%tagz._Artist-Title%"

I can't seem to find small, usable LUA scripts that doesn't bite their own tails and fork in every direction. I'm looking forward to take advantage of the complexity LUA offers, but right now it's really confusing. There are so many ways to do the same thing, and that makes it hard to take pieces from looks made by different people.

sprite artist
string include trackinfo
list rect int { 10 1 230 16 }
int fontsize 8
string fspec "%tagz._Artist-Title%"
list scripts string { "[function onmouseenter(this) look_setVisible(this, false) end]" }

I can't seem to find small, usable LUA scripts that doesn't bite their own tails and fork in every direction. I'm looking forward to take advantage of the complexity LUA offers, but right now it's really confusing. There are so many ways to do the same thing, and that makes it hard to take pieces from looks made by different people.

lua hideOnMouseOver
function onmouseenter(this)
    look_setVisible(this,false)
end

function onmouseleave(this)
    look_setVisible(this,true)
end
endlua

Note: You might also need to add setEnabled(this, false), depending on which sprite (buttons or artist) you declared first. Also, I did not do any code for showing the artist again onmouseleave.

Quote

Note: You might also need to add setEnabled(this, false), depending on which sprite (buttons or artist) you declared first. Also, I did not do any code for showing the artist again onmouseleave.

This is a good point, hiding the sprite with look_setVisible() does not disable it - that is it will still get mouse input and be clickable, etc.  look_setEnabled() will prevent the mouse input.  So use both functions as necessary depending on your needs.

Any ideas how I could get rid of that "bug" with the visualization?

Quote

Quote

Note: You might also need to add setEnabled(this, false), depending on which sprite (buttons or artist) you declared first. Also, I did not do any code for showing the artist again onmouseleave.

This is a good point, hiding the sprite with look_setVisible() does not disable it - that is it will still get mouse input and be clickable, etc.  look_setEnabled() will prevent the mouse input.  So use both functions as necessary depending on your needs.

Even worse, if you have an invisible (but enabled) sprite over other enabled and visible buttons that have hover states defined, the buttons underneath will respond to hovers and change image accordingly because you're entering the defined area of the look, but you can't press them because they're under the invisible sprite.

It took me forever to figure that out from scratch (as my buttons would respond perfectly to hovering, but not clicking). 

• look_getValue(presets, minvolume)
• fb2k_menuCommand("Foobar2000/Activate main window")
• look_setToggle(this, not look_getToggle(this))
• %_playlist_number%

string fspec "%_playlist_number%. [%artist% - ]$if(%title%,%title% ['['%album%[ #[%disc%/]$num(%tracknumber%,2)]']'],%_filename_ext%) ['('$upper($ext(%_filename_ext%))@%__bitrate%kbps')']"

Some issues that I need clarification/help with:

[/li][li]look_getValue(presets, minvolume)

[/li][li]fb2k_menuCommand("Foobar2000/Activate main window")

[/li][li]look_setToggle(this, not look_getToggle(this))

lua simpleToggle
-- User properties
toggle = 0

function onattach(this)
    look_setToggle(this, toggle)
end

function onleftbuttonup(this)
    if (look_getToggle(this) == 0) then
  look_setToggle(this, 1)
    else
  look_setToggle(this, 0)
    end
end
endlua

[/li][li]%_playlist_number%

Also, foo_looks crashes if you forget to put the file extension while defining the image that should be used..

You missed my previous reply

look_getValue("presets", "minvolume")

You have to quote the values you are looking up otherwise lua thinks they are variable names.

Not working well with 0.8 and has been well hashed out earlier in this thread.

Quote

• %_playlist_number%

Every sprite can be associated with a specifc playlist index.  By default it is -1 which means the "now playing" song meta data.  Since the playlist numbers are 0 based I add one in my custom tag parser - thus you are getting 0.

You can set the playlist index in the ski file with

sprite foo
int playlistindex N

in LUA

look_setPlaylistIndex(sprite,index)

This will format the text against the meta data for that specific index.

Note that once you set the playlistindex that is relative to the active playlist so will change the displayed text as you change playlists (tabs in the main ui).

I don't understand this at all. I don't think you understand what I'm trying to do. I just want to retrieve the number the playing song is in the playlist, so I can show it on my skin.

Hey all,

I'm new to making skins and well here is my first attemp after finishing the tutorial.

Fu Amp.ski (http://members.home.nl/robbertvanweelderen/skin/RobbertFuAmp.ski)
FuAmp.png (http://members.home.nl/robbertvanweelderen/skin/RobbertFuAmp.png)

I hope it works  

Robbert van Weelderen

Ohh and I forgot to say it's not finished, and I am looking forward to more tutorials.  (But I did find some mistakes in one of them.)

@UpNorth: I forgot to change it before uploading, everything should work now. 

Quote

Note: You might also need to add setEnabled(this, false), depending on which sprite (buttons or artist) you declared first. Also, I did not do any code for showing the artist again onmouseleave.

This is a good point, hiding the sprite with look_setVisible() does not disable it - that is it will still get mouse input and be clickable, etc.  look_setEnabled() will prevent the mouse input.  So use both functions as necessary depending on your needs.

section globals
string script "

    function enable(group)
  look_setVisible(group,true)
  look_setEnabled(group,true)    
    end

    function disable(group)
  look_setVisible(group,false)
  look_setEnabled(group,false)
    end
"

lua hideOnRollover
function onmouseenter(this) disable(this) end
function onmouseleave(this) enable(this) end
endlua

lua buttonsOnRollover
buttongroup = { prev, play, stop, next }
function onmouseenter(this) enable(buttongroup) end
function onmouseleave(this) disable(buttongroup) end
endlua

anza - after having a quick think about your vis problem, i realised that i do not have any magic tricks left up my sleeve for this one. the spillage on the right hand side can be dealt with when the playlist section is shown, but the spillage on the left cannot be hidden/masked. we have 3 choices as far as i can tell:
1. resize the spectrum
2. relocate the spectrum
3. ask danZ nicely if there is any way he can make foo_looks clip graphics that fall outside of the skin [span style='font-size:8pt;line-height:100%'](i think this option is very unlikely)[/span]
i didn't have this trouble with hand orb, because it was a circle window, and i was able to size the spectrum so it didn't spill out into the desktop area.
i will continue to think about this problem, but i think you should know.. it might end in tears   sorry.

sprite ratingback
int layer 3
int valign align.Near
int halign align.Near
list fontcolor int { 30 76 94 124 }
list rect int { 94 11 120 28 }
int fontsize 30
string fontname "GuinnessExtraStout"
string fspec "$repeat('*',6)"

sprite rating
int layer 3
int valign align.Near
int halign align.Near
list fontcolor int { 180 76 94 124 }
list rect ratingback.rect
int fontsize 30
string fontname "GuinnessExtraStout"
string fspec "$if(%rating%,$repeat('*',%rating%))"

@anza: I like this skin. But the font for Title is so big it could only fit a few characters. Why not split it into two lines with a smaller font? I have classical pieces here whose titles are huge. And how do you set the stars?

Quote

Quote

Note: You might also need to add setEnabled(this, false), depending on which sprite (buttons or artist) you declared first. Also, I did not do any code for showing the artist again onmouseleave.

This is a good point, hiding the sprite with look_setVisible() does not disable it - that is it will still get mouse input and be clickable, etc. look_setEnabled() will prevent the mouse input. So use both functions as necessary depending on your needs.

i solved this by making 2 global functions for micropanel; enable() & disable()

it combines visible & enabled into 1 function, and also works with groups of sprites

Code: [Select]

section globals
string script "

function enable(group)
 look_setVisible(group,true)
 look_setEnabled(group,true)
end

function disable(group)
 look_setVisible(group,false)
 look_setEnabled(group,false)
end
"

function show(this)
   look_setEnabled(this, true)
   look_setVisible(this, true)
end

function hide(this)
   look_setEnabled(this, false)
   look_setVisible(this, false)
end

minvolume = look_getValue("presets", "minvolume")
percent = 1 - fb2k_getVolume() / 100 / minvolume
look_setFspec(volumelabel, percent)

sprite volumelabel
...
string fspec "$sub(1, $div(%_volume%, %presets._minvolume%))"

lua hideOnMouseOver
function onmouseenter(this)
look_setVisible(this, false)
look_setEnabled(this, false)
end

function onmouseleave(this)
look_setVisible(this, true)
look_setEnabled(this, true)
end
endlua

sprite infoarea
list rect int { 10 194 11 15 }
list srcoff int { 388 2 11 15 }
list statemap int { 0 0 0 0 0 0 0 0 0 0 }
int layer 2
list scripts string { "hideOnMouseOver" }

DocUK - all of the problems you're having with playlistnumber etc. i had to deal with when i coded my fooAMP2 skin. check out the scripts in that to see if you can solve some of those hair-pulling problems you've encountered.
the script in question is lua updatePLnum. it simply keeps the plindex of all my tagz sprites up to date, which means that the details of the most recently played track remain displayed after you press stop. it only needs to be attached to one sprite, since it works independantly.
it's a bit of a pain the a$$, but don't blame foo_looks. in order to support full playlist display, danZ had to slightly break the old method of having a single playlist index number. tbh, it's the API's fault

lua playlistnumber
function update(this)
    look_setPlaylistIndex(this, fb2k_getNowPlaying())
end
function onattach(this)
   update(this)
end
function onplaybacknewtrack(this)
   update(this)
end
endlua

sprite songinfo
...
string fspec "%_playlist_number%. [%artist% - ]$if(%title%,%title% ['['%album%[ #[%disc%/]$num(%tracknumber%,2)]']'],%_filename_ext%) ['('$upper($ext(%_filename_ext%))@%__bitrate%kbps')']"
list scripts string { "playlistnumber"}

1) Is it ok to use three or more ski-files and put everything except the main ski-file inside a folder? I got the idea from AeroAmp by Aero, and IMHO it's easier to keep things organized this way. A positive side effect is that common files won't show up among the looks in preferences and another is that it is easy to delete a skin (one ski-file and one folder).

Quote

DocUK - all of the problems you're having with playlistnumber etc. i had to deal with when i coded my fooAMP2 skin. check out the scripts in that to see if you can solve some of those hair-pulling problems you've encountered.
the script in question is lua updatePLnum. it simply keeps the plindex of all my tagz sprites up to date, which means that the details of the most recently played track remain displayed after you press stop. it only needs to be attached to one sprite, since it works independantly.
it's a bit of a pain the a$$, but don't blame foo_looks. in order to support full playlist display, danZ had to slightly break the old method of having a single playlist index number. tbh, it's the API's fault

Is it not possible to just get the play list number onattach() and onplaybacknewtrack(), and then just store that. Because right now, the fspec changes everytime I switch playlist. Only the playlist number is correct now 

At the moment, I'm doing this:

Code: [Select]

lua playlistnumber
function update(this)
    look_setPlaylistIndex(this, fb2k_getNowPlaying())
end
function onattach(this)
   update(this)
end
function onplaybacknewtrack(this)
   update(this)
end
endlua

sprite songinfo
...
string fspec "%_playlist_number%. [%artist% - ]$if(%title%,%title% ['['%album%[ #[%disc%/]$num(%tracknumber%,2)]']'],%_filename_ext%) ['('$upper($ext(%_filename_ext%))@%__bitrate%kbps')']"
list scripts string { "playlistnumber"}

This is a simple question, but I haven't had the need to use this before now:

How do I set a color to be transparent in my sprites? I want the background to show through where the color is on those sprites.

you're right - i have omitted a volume control from micropanel - but i can easily add one

in fact, the vertical white bar was reserved for that very reason

to be honest - i wanted to know how important it was for people to have one.

i will have an update by the end of the day

Quote

This is a simple question, but I haven't had the need to use this before now:

How do I set a color to be transparent in my sprites? I want the background to show through where the color is on those sprites.

we removed this feature because you just have to make that area transparent, and then add { render.erase } to the start of the rendermap.

So transparent areas will only work with PNGs (and GIFs)?

Quote

Quote

This is a simple question, but I haven't had the need to use this before now:

How do I set a color to be transparent in my sprites? I want the background to show through where the color is on those sprites.

we removed this feature because you just have to make that area transparent, and then add { render.erase } to the start of the rendermap.

So transparent areas will only work with PNGs (and GIFs)?

I have the same problem (or at least I think I have).
Sometimes it seems to try to move the progressbar when you try to move the skin around, and I have NO idea what is causing this. Maybe tk32 could have a look at my .ski? And it doesn't even occur all the time.. Weid.

If you want to see some sort of text scrolling (done with TAGZ, so it's really ugly), download the new version (http://koti.mbnet.fi/antsau/foobar2000/orb.zip).

danZ:

A function to write to the foobar2000 console would be nice (for debugging).

LOG('hello, world!')

LOG("hello, world!")

LOG('variable x: '..x)

LOG(x..' + '..y..' = '..x+y)

Quote

danZ:

A function to write to the foobar2000 console would be nice (for debugging).

sorry

we forgot to mention this one

danZ & myself use it all the time for debugging

tk32, ok thanks for "solving" that problem

I'm just beginning to design the button that would make the playlist to slide out/back in, so I'd really appreciate if someone would write me the code needed for that (and of course for the playlist itself).
Also I wouldn't mind having a good text scrolling script that would scroll the text smoothly and not like I'm now doing it.

TIA.

Is it possible for two scripts assigned to the same sprite to share functions?

I want to do some abstraction, so my progress and volume bars can share some code (the code to get and set percentages, and to be dragged, etc). All my code is ready for merging, but one script doesn't seem to be able to see the others' functions.

sprite vol
list scripts string { "progAndVol[type=vol]" }

sprite prog
list scripts string { "progAndVol[type=prog]" }

lua relativeDisplacement
    
    myRect = { }
    MY = nil
    
    function displace(this, MY)

  myRect.x = look_getX(MY) + 10
  myRect.y = look_getY(MY)

  look_setX(pause,myRect.x)
  look_setY(pause,myRect.y)
    
    end

    function onleftbuttonup(this)
  displace()
    end

endlua

list scripts string { "relativeDisplacement[MY=play]" }

ERROR (foo_looks) : attempt to perform arithmetic on a nil value

Is it possible for two scripts assigned to the same sprite to share functions?

I want to do some abstraction, so my progress and volume bars can share some code (the code to get and set percentages, and to be dragged, etc). All my code is ready for merging, but one script doesn't seem to be able to see the others' functions.

I'm stuck again

How do I pass the name of a sprite to a LUA script in my common-ski?
This is the script I want to pass it to:

Code: [Select]

lua relativeDisplacement
    
    myRect = { }
    MY = nil
    
    function displace(this, MY)

  myRect.x = look_getX(MY) + 10
  myRect.y = look_getY(MY)

  look_setX(pause,myRect.x)
  look_setY(pause,myRect.y)
    
    end

    function onleftbuttonup(this)
  displace()
    end

endlua

and this is the line in my sprite where I try to pass the name of the sprite:

Code: [Select]

list scripts string { "relativeDisplacement[MY=play]" }

The code above gives me this error:

Quote

ERROR (foo_looks) : attempt to perform arithmetic on a nil value

, but if I change MY -> play (the name of the sprite I want to read the 'x' value from) it works. One problem is that I don't know how to initialize "MY", and the other is that I don't know how to use it to pass the name of a sprite ('play').

What I'm trying to do is to make a script that places buttons relatively to each other (in this case the pause button relative to the play button). Right now I do it with a onleftbuttonup, in a temporary sprite just because I don't know how to make this happen "by itself" on startup (I have tried a couple of things woth onattach(), but I can't get it to work).

I hope some of this makes sense and that someone can help me...

it will take a little more time than danZ expected

because you can't simply re-use the tray code he had written for the default look

the tray code simply slides out the tray, but your tray is bigger than the whole skin, so your tray will need to grow in size rather than slide

Quote

Quote

Quote

This is a simple question, but I haven't had the need to use this before now:

How do I set a color to be transparent in my sprites? I want the background to show through where the color is on those sprites.

we removed this feature because you just have to make that area transparent, and then add { render.erase } to the start of the rendermap.

So transparent areas will only work with PNGs (and GIFs)?

PNG is the recommended file type

but gif is usable (if you don't mind using only 256 colors, and having jagged edges)



bernard - i will add the volume control very soon, but it will still be the delayed volume kind. there is no way to code any other type at the moment

for an example of what it will be like, try the orange volume bar in URMEL's skin that i coded for him recently.

URMEL's skin + tk32's custom volume bar
skin_raw.png (http://www.btinternet.com/~sean.m.kelly/skin_raw.png)
skin_raw.ski (http://www.btinternet.com/~sean.m.kelly/skin_raw.ski)

Is it not possible to just get the play list number onattach() and onplaybacknewtrack(), and then just store that. Because right now, the fspec changes everytime I switch playlist. Only the playlist number is correct now 

Quote

Is it not possible to just get the play list number onattach() and onplaybacknewtrack(), and then just store that. Because right now, the fspec changes everytime I switch playlist. Only the playlist number is correct now 

This is why there is a concept of now playing (-1) and a specific playlist index.  Now playing is its own meta data and not associated with any playlist or playlist index and that is why is only shows up if foobar is playing.  Also, it remains even as the playlist is changed.  The con is that there is no playlist number.

Using a specific playlist index means you can show playlist number, have the text formatted regardless of the playback state (playing, stopped, etc.), but it changes with any changes in the playlist.

This is just the way the foobar API works.  It makes sense if you really sit down and think about it (which I did when dealing with this issue during development).  foo_looks 1.0 was somewhat flawed in the area of text formatting IMHO.

Quote

anza - after having a quick think about your vis problem, i realised that i do not have any magic tricks left up my sleeve for this one. the spillage on the right hand side can be dealt with when the playlist section is shown, but the spillage on the left cannot be hidden/masked. we have 3 choices as far as i can tell:
1. resize the spectrum
2. relocate the spectrum
3. ask danZ nicely if there is any way he can make foo_looks clip graphics that fall outside of the skin [span style='font-size:8pt;line-height:100%'](i think this option is very unlikely)[/span]
i didn't have this trouble with hand orb, because it was a circle window, and i was able to size the spectrum so it didn't spill out into the desktop area.
i will continue to think about this problem, but i think you should know.. it might end in tears   sorry.

Well I guess I'll just have to resize the spectrum then. I'm going to have to see what I can come up.

Quote

Quote

Is it not possible to just get the play list number onattach() and onplaybacknewtrack(), and then just store that. Because right now, the fspec changes everytime I switch playlist. Only the playlist number is correct now 

This is why there is a concept of now playing (-1) and a specific playlist index.  Now playing is its own meta data and not associated with any playlist or playlist index and that is why is only shows up if foobar is playing.  Also, it remains even as the playlist is changed.  The con is that there is no playlist number.

Using a specific playlist index means you can show playlist number, have the text formatted regardless of the playback state (playing, stopped, etc.), but it changes with any changes in the playlist.

This is just the way the foobar API works.  It makes sense if you really sit down and think about it (which I did when dealing with this issue during development).  foo_looks 1.0 was somewhat flawed in the area of text formatting IMHO.

Well alright, I think I understand how it works now. Do you have any suggestions for how I could grab artist, title, album, tracknumber, bitrate, and format from the Now Playing index (-1), and the playlist number from the active playlistindex?

lua myformat

spec = ""

function onplaybackstart(this)
    updatetext(this)
end

function onplaybacknewtrack(this)
    updatetext(this)
end

function updatetext(this)
     local index = fb2k_getNowPlaying()
     local text = fb2k_formatTitle(index,spec,nil))
     look_setText(this,index..": "..text)
end

endlua

sprite nowPlaying
string fspec "" // don't set the fspec
list scripts string { "myformat[spec='%artist% and whatever']" }

I have a question about the rendermaps. I don't understand the significance or the use for them. I mean, if I don't specify any fillcolors, will not specifying render.Fill improve performance? Why would you want to not render something you have specified as well?

I don't get it, can you please explain 

Quote

I have a question about the rendermaps. I don't understand the significance or the use for them. I mean, if I don't specify any fillcolors, will not specifying render.Fill improve performance? Why would you want to not render something you have specified as well?

I don't get it, can you please explain 

You can use the render map to control what gets rendered AND/OR the order.

sprite textonly
list rendermap int { render.Text }

sprite textonfill
list rendermap int { render.Fill render.Text }

sprite fillovertext
list rendermap int { render.Text render.Fill }

sprite textoverimage
list rendermap int { render.Text render.Image }

sprite nothing
list rendermap int { }

By default the render map is { render.Image render.Fill render.Text render.Border }

Its true you can set null text, invisible colors, etc. which gives the same effect as removing items from the render map but I did it this way so that you could just define a fill color and then get a fill, etc. with out dealing with render map.

Render map is for advanced users/uses.

Quote

Quote

I have a question about the rendermaps. I don't understand the significance or the use for them. I mean, if I don't specify any fillcolors, will not specifying render.Fill improve performance? Why would you want to not render something you have specified as well?

I don't get it, can you please explain 

You can use the render map to control what gets rendered AND/OR the order.

sprite textonly
list rendermap int { render.Text }

sprite textonfill
list rendermap int { render.Fill render.Text }

sprite fillovertext
list rendermap int { render.Text render.Fill }

sprite textoverimage
list rendermap int { render.Text render.Image }

sprite nothing
list rendermap int { }

By default the render map is { render.Image render.Fill render.Text render.Border }

Its true you can set null text, invisible colors, etc. which gives the same effect as removing items from the render map but I did it this way so that you could just define a fill color and then get a fill, etc. with out dealing with render map.

Render map is for advanced users/uses.

What effect does specifying a rendermap have on performance?

sprite fillovertext
list rendermap int { render.Text render.Fill }

sprite textoverimage
list rendermap int { render.Text render.Image }

Quote

sprite fillovertext
list rendermap int { render.Text render.Fill }

sprite textoverimage
list rendermap int { render.Text render.Image }

This looks inconsistent to me. The last one is "imageovertext" isn't it?