And now for another Beta of Pocket SharpMT. 1.3 Beta 4 has a few bug fixes and two new features, which keeps it on par with SharpMT (1.3/Beta 1) which got a couple of new features last week. Download Beta 4 and read the FAQ for more info.
Bug fixes have been centered around the connection methods, of which I have little control over. Been reading through the user comments and fixing things as I go, but in most cases (i.e. Assembly errors or just random MT failures) I can only fix so much, especially if I can’t duplicate them here. Having said that, I was still able to make a couple of tweaks here and there.
The two new features are sorta minor but useful. One is the “I’ve been published” icon that is now a part of SharpMT. Basically, in the “Open Draft” window there’s a plain document icon for drafts that haven’t been sent to the server and a document with a green arrow for drafts that have. If you publish a draft and then re-save the draft locally, the arrow will disappear until it is re-posted. Unlike its desktop counterpart, Pocket SharpMT has no way of changing this flag at this time.
The other new feature is a new tab on the main window: Authored On. By default “Use Server Time” is selected meaning that MT decides the date and time set to your new post; this is how Pocket SharpMT has worked up to now. If you uncheck “Use Server Time” you can then select a specific date and time for your new post.
Updated screenshots:
Download Pocket SharpMT 1.3 Beta 4 now!
Seems to work just fine. Still getting the resource assembly error, but I think I tracked it down even further. I think that error my appear when P#MT can’t connect to the server or gets a disconnect from the server as I generally receive an error “Could not connect to blog server” immediately afterwards. My connection from the middle of the ocean is sometimes full of noise and I may be getting timeouts or disconnects which are generating the errors, especially since I am the only person affected with this it seems.
I posted after receiving the error and the post went through flawlessly. The line quality may also answer why it only happens intermittently, but why it always happens in relation to categories, I have no clue.
On another note, is it possible to just post links to the CAB files? That way we can update directly from the PPC through PIE, and get just the files we need.
So it’s the connection handling on the post, but not on the first but the second connection that is trying to set the categories… interesting. At least I know where to look.
Ya, for Beta 5 I’ll post the CABs as well as the ZIP; I doubt I’ll do a full installation for this project, so it’s no hardship :)
Its pretty random which connection its dying on.
Sometimes its when refreshing categories (Which causes the most problems), sometimes during Set Categories during post. Its pretty random.
Well, refreshing categories on it’s own is thread-less already, so there’s little more I can do in there, but the posting is now thread-less as well in Beta 5. If the connection gets pulled out from under Pocket #MT and the framework doesn’t except on me, I’m pretty much oblivious to it…