Quote:
Originally Posted by zemog
@qwerpoi
One more time
|
Thanks for the translation update, I updated the links accordingly.
Quote:
Originally Posted by TheRainmaker
If you still got a problem to open AvsP try this;
Delete all of things about AvsP aplication and if you still have zipped file(or download again) extract again in any folder...
It will be work %100...
|
Yes, you're right, you only need to delete _last_session_.ses for things to work. The problem is is that if you have scripts with unicode in them, it's possible for the issue to come up again. I'll try and have this bug squashed once and for all in the next release.
Quote:
Originally Posted by foxyshadis
I've been trying out the new syntax highlighting tools, now that the function definitions are all up-to-date, and I'm loving it! =D I was wondering if you think it'd make sense to highlight the function argument names, and maybe extend the comment background to the edge of the window.
|
Some good suggestions, I'll see what I can do.
Quote:
Originally Posted by foxyshadis
Also, have you had any word about how well avsp runs on *nix systems? Just curious.
|
Although wxPython is cross-platform, AvsP uses some windows-specific functions, particularly in the video display code, which calls up on avifil32.dll and msvfw32.dll via the ctypes python package (although currently the display code is being rewritten by tsp to utilize avisynth.dll instead of avifil32.dll...). The display code is pretty well separated, so making AvsP cross-platform shouldn't be too much work (in theory). Of course, unless I'm missing something, it's not an issue until Avisynth 3.0 comes out. Whenever that happens, the display code can be rewritten to utilize the interfaces that Avisynth 3.0 would provide.
Quote:
Originally Posted by foxyshadis
|
Thanks for the info, I'll give it a look over. And yes, you should be able detect when a file or folder is activated in python using ctypes and win32 itself (here's a
link if you're curious). Of course, that would be adding even more windows-specific code...
Quote:
Originally Posted by Alain2
Only one small request: can the syntax highlights have priority on the "Highlight current line" option ? Meaning,when a background color has been defined in some syntaxe highlight, can it stay even when the line is selected (and therefore highlighted)?
|
Thanks for the translation update. As far as highlighting priority is concerned, I'm not sure if it's possible, but I'll check it out.
Quote:
Originally Posted by Alain2
The new macro created lots of new inputs with the arguments in the functions definition, that's nice ; do you think it would be possible for it to distinguish between required and optional parameters, and add " for the arguments accordingly ? But maybe this information is not available from avisynth 2.5.7...
|
I don't know too much about AviSynth's internals, so whatever tsp and foxyshadis said
. Perhaps if we're looking to the future, it would be possible to enforce plugin design in Avisynth 3.0 to specify which arguments are defaults and which are required, and furthermore specify ranges of allowable values for each argument, which would lead to the ability to automatically create user sliders for each filter. Which is not an important feature to me, but people seem to like going crazy with those user sliders
.