火车订票助手受到媒体推荐

很巧合的一个日子,3月15日——国际消费者权益日,《萧山日报-数字报纸》发表的《爱上掌上旅游生活》一文,推荐了目前最热门的几款旅游方面的应用,火车订票助手赫然在列,下面是《萧山日报》对火车订票助手的评价:

    •火车订票助手

虽然这款软件在APPSTORE上是收费软件,价格高达18元,但是作为一款专门为中国铁路客户服务中心网站定制的客户端订票工具,它的强大功能还是值得肯定的。你可以在手机上完成车次查询、下单、付款、退票等一系列操作,甚至还支持批量购票操作,一次最多可以购买5张火车票。而最终的取票在火车站的自助售票机上完成,不用担心假火车票的问题。

实用指数:★★★★☆

火车订票助手受到媒体的推荐,很让我们感到惊喜,但是却也是情理之中。我们一直都在致力于为用户创造更好的软件,为用户提供更好的服务。火车订票助手由专业团队精心打造,一经发布便受到了热烈的欢迎,作为一款App Store旅行分类排行榜名列第一的优秀订票软件,火车订票助手受到媒体的推荐,也不是件偶然的事情。这里有一点要纠正的是,火车订票助手的定价是非常实惠的,18元的定价仅仅相当于在火车票代售点购买3张火车票的手续费+3元零头。

媒体的推荐,对于我们是一种肯定和鼓励,我们将再接再厉,一如既往的为广大用户提供更好的软件和服务。

查看萧山日报对火车订票助手的评价:

《萧山日报-数字报纸》2012年3月15日《爱上掌上旅游生活》

从苹果App Store应用商店下载火车订票助手

CHM+ Reader 2.3 Released

We are glad to announce the release of CHM+ Reader 2.3, which brings support for .mht file format.

What’s new in CHM+ Reader 2.3:

– support for .mht file format (experimental)
– ability to send any document to email
– improve the stability of highlight feature
– support opening unknown document as text file
– improved web upload UI

Get CHM+ Reader

Get CHM+ Reader Lite

CHM+ Reader 2.2.1 Released

We are glad to announce the availability of CHM+ Reader 2.2.1, which brings update for iOS 5 and optimization for iPad.

What’s new in CHM+ Reader 2.2.1:

– optimize UI for iPad (“File Transfer” & “Table of Contents”)
– turn off iTunes/iCloud backup by default for iOS 5
– bring back the “Define” menu for iOS 5
– new setting option to enable/disable image resizing

Get CHM+ Reader

Get CHM+ Reader Lite

ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry ‘1’ for key ‘PRIMARY’

I got this error while trying to add auto_increment attribute to a MySQL table field:

ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry ‘1’ for key ‘PRIMARY’

After some googling I found the solution: simply remove the record with ‘0’ for the primary key field. It seems that MySQL tries to adjust ‘0’ to ‘1’ for auto_increment field.

CHM+ Reader On Sale Now

The sale is over, thanks everyone!

CHM+ Reader is now on sale for the winter holidays ($5.99 => $2.99), purchase and save 50% now!

CHM+ Reader is the best CHM reader for iPad, iPhone/iPod touch, why not get it now?

Search for “CHM+ Reader” in iTunes or open the follow URL to purchase:

https://itunes.apple.com/app/chmplus-chm-reader/id441521818?mt=8

CHM+ Reader 2.2 Released

We are glad to announce the availability of CHM+ Reader 2.2, which is a significant update that includes many new features.

What’s new in CHM+ Reader 2.2:

– highlight / annotation and bookmark
– search functionality (find in page)
– look up words with Google / Wiktionary
– setting option for enabling/disabling double tap to enter/exit full screen
– optimize TOC UI to display long titles
– support for MS Office 2007 document format: .docx, .xlsx, .pptx
– change the built-in external link browser theme to default color
– fix UTF-8 encoding issue that exists in some CHM documents

CHM+ Reader is available on iTunes App Store:

Download CHM+ Now Download CHM+ Now

Download CHM+ Lite Now Download CHM+ Lite Now

CHM+ 2.0 Released

CHM+ (ChmPlus) 2.0 is now released and many new features has been added:

– supports file uploading with FTP
– supports organizing documents with folders (via FTP)
– long tap to save image for CHM documents
– long tap to open document in other applications
– supports PDF, HTML, text files and images
– supports office files (DOC/PPT/XLS/RTF/Keynote/Numbers/Pages)
– supports audio and video
– fix CHM character encoding issue

CHM+ is available on iTunes App Store:

Download CHM+ Now Download CHM+ Now

Download CHM+ Lite Now Download CHM+ Lite Now

Application failed codesign verification

I got this warning while compiling my app for uploading to Apple App Store:

Application failed codesign verification.  The signature was invalid, or it was not signed with an Apple submission certificate. (-19011)

After spending plenty of time searching for the solution, still no luck.

I finally found out that it was because I had set the codesign provision to be automatically select. After I set the codesign provision manually everything is fine.

Hope this will help those who encounter the same problem.

Debugging EXC_BAD_ACCESS

This article is from http://www.cnblogs.com/junz/archive/2010/05/23/1742118.html , useful for debugging the annoying EXC_BAD_ACCESS exception.


You have to accept the fact that sooner or later you will need to debug an EXC_BAD_ACCESS problem and most probably won’t be easy to.

This article however is about how to make the process easier, in some cases easy as a piece of cake.

What does EXC_BAD_ACCESS mean?

EXC_BAD_ACCESS means that message was sent to a point in the memory where there’s no instance of a class to execute it. Thus “bad access”

When EXC_BAD_ACCESS happen?

You will get EXC_BAD_ACCESS in 3 cases:

  1. An object is not initialized
  2. An object is already released
  3. Something else that is not very likely to happen

That’s already a good starting point. Start using the debugger, if you recently added a new object to the class you’re working on, put a breakpoint at the line before the freshly added object is used for the first time and check the values in the debugger.

What’s happening most though is that you will be sending a message to an overreleased object – i.e. object that is gone from the call stack. In this cases everything (and indeed everything) you will get in the console will be just :

EXC_BAD_ACCESS.

This is because the object is gone, there is no information what class was it, or what source file or anything else. That’s really tough to debug with NSLog … NSLog is helpful, but you need to put 1,000 NSLogs around to fetch where is the problem.

Enabling NSZombies

The solution to overreleased objects are the zombies. When this feature is enabled, a dummy object (a zombie) is kept on the place of every released object, thus allowing to debug objects which were released already. Very easy to enable:

  1. Double click your executable in the “Executables” in XCode
  2. Open “Arguments” tab
  3. In “Variables to be set in the environment” (that’s the list at the bottom, be careful which one you edit) click the “+” button and for name of the variable enter “NSZombieEnabled” and for value “YES”

Voila!

Now instead of wondering what’s going on and which exact object produced the problem, you’ll see exactly which class is the trouble maker, and you’ll debug it quite fast.

Beware the zombies though

Just a reminder not to leave the zombies enabled, when you submit your app to the App store. Also, it’s a good practice to disable them if you don’t really need them.

All the sizes of iOS app icons

  1. 57 px, iPhone – good ol’ classic.
  2. 72 px, iPad
  3. 114 px, iPhone 4 – make sure your icon shines on the Retina Display.
  4. 512 px, iTunes – Used in iTunes and in the App Store, where it’s sized down to 175 px. Sadly, you can’t provide the 175 px version directly.
  5. 29 px, iPhone Settings/Spotlight, iPad Settings – used in these table views. Minor, but still important!
  6. 48 px, iPad Spotlight – yup, the iPad uses a different size for Spotlight and Settings. This size is controversial! Apple’s docs actually say the icon is 50 px, but then there’s this note: The final visual size of this icon is 48 x 48 pixels. iPhone OS trims 1 pixel from each side of your artwork and adds a drop shadow. Be sure to take this into account as you design your icon. How weird!
  7. 58 px, iPhone 4 Settings/Spotlight – that’s right, you have to make both 57 and 58 px versions of your icon – d’oh! Good luck aligning this if there’s a line running down the middle of the icon.
  8. 64 px document icon – who knew: iOS apps can provide document icons. It’s unclear how these will be used – they don’t do much currently – but it’s not a bad idea to start planning now.
  9. 320 px document icon – why not 256, darn it? :)
  10. Let’s say Apple comes out with a high-ppi iPad. That will mean at least 2 new sizes – maybe 144 px and 96 px.

From:  All the sizes of iOS app icons (Neven Mrgan’s Tumbl)