Dr. Ralf S. Engelschall
Dr. Ralf S. Engelschall
Sure, if it is clean definition I'll take it over, of course,
The problem is that XTerm 3.0 has a dramatically different API and internal screen rendering and I until now was not able to get blessed-xterm running with it.
In my code comment for the clone() usage, I wrote: "clone options or all widget instances will show at least the same style, etc" How do you think this issue...
I've currently no time to reproduce, but AFAIK the issue was that the style of a window being rendered active, or scrolling (in visual mode) or in error state was...
This should be done with the next major version 1.1.0. I think it can be done rather easily because internally ComponentJS already has two APIs: an imternal and external one.
Good catch: I'll try to let ComponentJS check for already spooled actions on state changes in the future. Remarked.
I'm not sure I really understood the problem. You mean you do a cs(...).state("visible", function () {....}) within a guarded section and that the callback function is called even if...
Ah, I see, I see. Very interesting code. You use "sync: true" to request a synchronous state transition of component which guards itself for 2sec. Well, yes, the result is...
I've not tried FFmpeg output for some time myself, so I've to check this.
I can confirm that FFmpeg support is currently broken. I'm also not able to record or stream with FFmpeg. I'm already debugging it, but it looks strange: FFmpeg is started...