| Blog |
|
| Releases |
Page:
0 ... 5 ... 10 15 16 17 18 19 20 21 22 23 ... 25 ... 30 ... 35 ... 40 ... 45 ... 50 ... 55 ... 60 ... 65 ... 70 ... 75 ... 80 ... 85 ... 90
| Scribe issues with Aspell and PHP | |
|---|---|
|
Date: 31/5/2010 | If like me you do a little PHP as well as use Scribe, then you might find that one day your spell checking functionality in Scribe just stops working, and instead all words are returned as spelling errors despite having the dictionaries correctly installed and configured.
This is because your PHP directory is in the PATH and also has an aspell-15.dll and Scribe is loading that instead of the one in your aspell install (usually C:\Program Files\Aspell\bin). The fix is to more the aspell folder so that it's before your PHP folder in the list of folders in your PATH. Btw I quite like Path Editor for that purpose. |
| (0) Comments | Add Comment | |
| Visual Studio 2010 Express Registration Key | |
|---|---|
|
Date: 12/5/2010 | 6VPJ7-H3CXH-HBTPT-X4T74-3YVY7
Just FYI you know. |
| (3) Comments | Add Comment | |
| Pinnacle VideoSpin | |
|---|---|
|
Date: 10/5/2010 | If you ever consider downloading and using Pinnacle VideoSpin, stop... turn around... and run away as fast as you can. It takes the definition of crap to new levels. Lets see:
Like I said... run away. Run far far away. That is all. |
| (0) Comments | Add Comment | |
| Application Crash Handling | |
|---|---|
|
Date: 5/5/2010 | I've got a number of outstanding Scribe bugs that involve crashes at the moment so I've been trying unsuccessfully to collect crash dumps and work out where the crash happened. The existing system writes a minidump to a file and I should be able to use that to find the stack trace of the crash and what threads were doing what. However the reality is that when I get all my symbols and binaries lined up VS2008 (express) fails to match the .PDB's with the binaries. I know that I have all the right files and paths, but I guess it just can't cope with VC6 built binaries/symbols.
So where does that leave me? I'm downloading VS2010 express at the moment to try and build Scribe/Lgi with so that I can try postmortem analysis with that. Hopefully the minidumps from a VS2010 build will seamlessly load into VS2010 and work. I already have good systems in place with the saving of symbols during my release process, but I need to close the loop so that crash dumps get reported back to me more autonomously. This week I added proper version information to the version resource on the windows builds. That is handled by a custom build step running a python script that pulls the scribe version and build identification and the current SVN revision and then embeds that into the Resource.rc file so that it ends up in the version resource of the final binary. When the application crashes I try and load that information in to use as the filename of the crash dump so that you get something like this: InScribe-2.00.24.4774-crash.dmpSo in the near future I'm planning to add some code that scans the install folder for .dmp files and offers to upload them to memecode.com to report the crash. Then I can collect them and fix the problem. In theory. |
| (0) Comments | Add Comment | |
| I <3 Python | |
|---|---|
|
Date: 22/4/2010 | I've been in a somewhat reflective mood since I posted that comment about not being sure I'll still be coding in C++ in 5 years time. And yesterday I had reason to do a little scripting. So I decided to break out the python interpreter to write a wrapper around mp4box to convert a raw AAC file into a MP4. I attached that to the context menu for .aac files on my WinXP box and it just works nicely.
So today I wanted a similar script for compressing/decompressing bzip2. So I wrote one and attached it to the "*" files and folders context menu. Nice. This is much better than those weird little DLL's that are available for the same tasks. And I can see all the behavior under the hood and modify it if need be. Tomorrow? "Open Command Prompt Here", "Copy My Path"... etc, the skies the limit! I'm officially a python programmer (yeah ok, I know enough to be dangerous lol). Update: Opps I wrote a working FLV demuxer in Python. So now I can go FLV -> aac/mp4 audio file in one step. How hard would be it to hook that up to a youtube page? *wink* |
| (0) Comments | Add Comment | |
| Scribe v2.0 Final | |
|---|---|
|
Date: 14/4/2010 | Well according to the Bug DB all the P1 and P2 bugs are fixed (although not all fixes released yet) and there are just 5 P3's standing between me and a v2 final release. If I go by my self imposed metric of all P1, 2 and 3 bugs fixed for the final release.
So far no one is complaining about that so yeah I forge on ahead. This could mean that if I knock those over I need to setup the upgrade process for people. I recently fixed the InScribe purchase page to correctly show the key and download on checkout. But I'll have to revisit all that for people upgrading to v2 from v1. I'm hoping that Beta23 will be the last beta, and basically the next build after that will enable the new key system for v2 and that'll be the finished retail build. Some 'n' years late... I don't know what 5 years ago I started this re-factoring thing? A few failed attempts and then I finally settled on an API and a new backend DB format. Update: 2 left... and I'm wondering how important this one really is. The mail3 format doesn't allow folder loads to be done incrementally, in that I run the query, and control doesn't return to my code until the query has finished executing... meanwhile the app hangs. So there is no opportunity for me to update a progress bar. Finished? Maybe... the bugs are now all dealt with, but there are some non-bug related things to process before the last (??) beta becomes the "Final" build:
|
| (3) Comments | Add Comment | |