Version 0.8.23:
* Added function to split user options for first and second pass
* Added new editor window for user options (optimized for 2 passes)
* Added option to skip audio encoding in the first pass of two
* 2-pass togglebutton uses toggle event instead of click (used to switch
no audio togglebutton in sensitivity)
* Added second command line editor to confirmation window for 2 passes
* Added new crop and scale type (w:h:x:y)
* Version is read from version file
* Bug in createProgress(): try to destroy window before creating a new one
(progress window 1 of 2 passes didn't piss off and rejected removal via
the optional close button)
* Bug in presetFormat(): convert values to string before regexing against
True/False (backward compatibility for new option 'no audio')
* Changed regex in presetFormat to check for more chars as string
This article was published
Montag,, 24. Januar 2011 @ 04:00.
You may want to subscribe to the comments via RSS 2.0 feed.
Post a comment, or create a trackback on your page.
Write a comment / Schreibe einen Kommentar (traGtor 0.8.23: new 2-pass features and bug fixes)
Please note that comments are moderated and don't appear immediately. If you're reporting a problem or a bug I'll publish them when I started processing your request.
Bitte beachte: Kommentare sind moderiert und erscheinen nicht sofort. Ich veröffentliche Bugreports und Hilferequests erst, sobald ich mich eines Problems oder Bugs angenommen habe.
Thank you very much!! You're doing an essential job for the development of open source software! The following points aren't meant as dogmas but as a clue, decide for yourself what you think could be useful in troubleshooting.
- Please...
- ...state name and version of your operating system / desktop environment
- ...state the version of the program you're using
- ...be detailed in what is happening and what you expected to happen
- ...try to provide some deeper information (like xplanetFX logs or the output of the program when started in a terminal window)
- ...speak to me as a human being, don't think I'm a bot.
Herzlichen Dank!! Fehlerberichte sind essentiell für die Entwicklung von Open-Source-Software! Die folgenden Punkte sind keine Dogmen, sondern sollen eher Anhaltspunkte darstellen; entscheide selbst, ob sie für die Fehlersuche hilfreich sein könnten.
- Bitte...
- ...nenne den Namen und die Version Deines Betriebssystems / Deiner Desktopumgebung
- ...nenne die Version des von Dir benutzten Programms
- ...beschreibe möglichst genau, was passiert und was Du erwartest, was passieren sollte
- ...stelle möglichst tiefergehende Informationen zur Verfügung (xplanetFX Logs oder die Ausgabe des Programms im Terminalfenster)
- ...sprich mit mir, wie mit einem Menschen, ich bin kein Automat.