There is `Function.caller` (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/caller), which can be abused to get the name of the function. But this will not be performance friendly (constant regexp parsing) and this method is unavailable in strict mode anyway.

function show_callback_name(debug){
	if (debug){
		var myName = arguments.callee.caller.toString();
		myName = myName.substr('function '.length);
		myName = myName.substr(0, myName.indexOf('('));
		console.log("_________________ " + myName + "() _________________")
		console.log(window.Width, window.Height);
		console.log("Panel: " + Math.round(window.PanelMemoryUsage * 0.000001) + " MB");
	}
}

Retrieving caller information was deemed a problematic feature for multiple reasons:
- Makes some optimizations impossible.
- Easy to abuse to make code unreadable.
- (Web-specific) potential security vulnerabilities.

function Container(){
	this.items = [obj1, obj2, obj3...];
	this.forward = (method, ...args) => {
		this.items.forEach((item) => {
			if (method in item) item[method](...args);
			if ('forward' in item) item['forward'](method,...args);
		});
	}
}

Are you using SMP panel as a standalone CUI/DUI panel? Or is it a part of smth like PSS?

For reasons I don't understand, it only works with columns ui, maybe some more advanced coder can figure out why,

But today I found out that the second on_size() sets the window to an intermediate measure, which my code was not expecting.

I am facing the following message after installing the latest fsmp version.
I am using latest foobar 1.5 and I have attached a report of installed components.

I could not reproduce this behaviour, do you have a reproducible scenario?

function on_size(){
    console.log("width: " + window.Width, "height: " + window.Height);
}

nk=msg=978394 date=1576492529]
Regarding repeated on_size calls: these are only invoked when the panel receives WM_SIZE message (except for one extra invocation which will be removed in the next version. These messages might be triggered by fb2k, by DUI, by CUI or by system itself. SMP just translates this native system message to JS callback.

width: 0 height: 0
width: 1364 height: 653

Quote from: davideleo on 2019-12-09 17:14:04

But today I found out that the second on_size() sets the window to an intermediate measure, which my code was not expecting.

I could not reproduce this behaviour, do you have a reproducible scenario?

Regarding repeated on_size calls: these are only invoked when the panel receives WM_SIZE message (except for one extra invocation which will be removed in the next version. These messages might be triggered by fb2k, by DUI, by CUI or by system itself. SMP just translates this native system message to JS callback.

Quote from: zoumbro on 2019-12-13 06:14:31

I am facing the following message after installing the latest fsmp version.
I am using latest foobar 1.5 and I have attached a report of installed components.

You probably didn't install all the required fonts (which are listed in readme.md in samples folder).

include(fb.ComponentPath + "docs\\helpers.js");

let font = gdi.Font("segoe UI", 16);
let myRegion = new PaintRegion(100, 100, 200, 200)


function on_paint(gr){
	gr.FillSolidRect(0, 0, window.Width, window.Height, colours.DarkGray);
	gr.GdiDrawText("TEST", font, colours.White,110, 70, 100, 20)
    myRegion.paint(gr);
}


function PaintRegion(x, y, w, h){
    this.x = x;
    this.y = y;
    this.w = w;
    this.h = h;
    this.paint = (gr) => {		
		gr.FillSolidRect(this.x, this.y, this.w, this.h, colours.Pink);
        var clipImg = gdi.CreateImage(this.w, this.h)
        var grClip = clipImg.GetGraphics();
		
			grClip.GdiDrawText("TEST", font, colours.White, 10, 10, 100, 20)		
			grClip.DrawEllipse(100, 50, 200, 200, 2, colours.White);
			
        clipImg.ReleaseGraphics(grClip);
        gr.DrawImage(clipImg, this.x, this.y, this.w, this.h, 0, 0, this.w, this.h)
    }
}

How can I avoid this blurred effect?

Upon reading some window .NET docs on GDI+ and TextRender, I have the impression that the use of DrawString is strongly encouraged, whereas I get the opposite idea from the SMP docs. Are the two methods actually the same? And what are the drawbacks of replacing DrawText with DrawString, anyway?

GdiDrawText
    Provides faster and better rendering than GdiGraphics#DrawString.

    Do not use this to draw text on transparent background or with GdiGraphics other than the one passed in on_paint callback: this will result in visual artifacts caused by ClearType hinting.
    Use GdiGraphics#DrawString instead in such cases.

DrawString is worse than DrawText in most cases. DrawText has better performance and better rendering unless used on a transparent surface (as mentioned in SMP docs).
One of the sources: https://stackoverflow.com/questions/1203087/why-is-graphics-measurestring-returning-a-higher-than-expected-number/6404811#6404811

Firstly, MERRY X MAS! and thx for the great component.
It looks like DrawImage() in SMP is generating left and top border by default. How can I avoid this?

o/
What version of SMP are you using?

function drawImage(gr, img, src_x, src_y, src_w, src_h, auto_fill, border, alpha) {

	if (border) {
//		gr.DrawRect(src_x, src_y, src_w - 1, src_h - 1, 1, border);
	}
}

-eidt-
I digged google a little bit, it looks like borders are generated during resizing images
https://mariusschulz.com/blog/preventing-ghost-borders-when-resizing-images-with-system-drawing

Does someone there have an idea? Thanks!