This was a long time strategic decision we did when WordPress moved to custom post types. Since the large majority of our users didn't want every single event to act as a blog post, we separated them out. Pro simply add some extra functionality and isn't any different.
I can imagine that some of you would prefer the previous approach. We've been trying to think of some ways in which event creators can facilitate bridging the gap without having to do double entry. If you have any specific suggestions we would love to hear them.
That said, if you were using custom fields (real WordPress custom fields, not our events fields), you can turn on custom fields by adding a couple words to the "the-events-calendar.class.php file in /lib/.
protected $postTypeArgs = array(
'public' => true,
'rewrite' => array('slug' => 'event', 'with_front' => false),
'menu_position' => 6,
'supports' => array('title','editor','excerpt','author','thumbnail', 'custom-fields')
All I am really doing is adding ", 'custom-fields'" at the end of the supports array.
Of course if you make this change, you'll need to remember to add it back if you update. Let me know if that doesn't work and we can figure it out.
Since we are now going to be doing a fair bit of work on the open source plugin since it is the core of our framework, there may be some updates in the near future.