In this example, you are already defining a height in your style, so the middle text tag is getting confused when you define a second height.

What is actually happening here is that you are trying to define a height to fit without defining a font size or font type. Since it is sizing to itself, it has no reference. While these have default values in normal situations, the fit can't discern the defaults.

I have updated the documentation to say as much. Thanks for helping me understand this.

Also note the you must define height="fit" on the text tags as it won't work in a style tag.

Here is what it could look like:

<wire>

<styles>
<style name="textbox" height="fit" width="300" borderwidth="3" bordercolor="#ff0000" background="#7f7f7f" leftinset="20" size="18" font="helvetica"/>
</styles>

<main>
<panel name="body" width="100%" height="100%">
<text name="block1" style="textbox" height="fit" text="top text box" />
<text name="block2" style="textbox" height="fit" valign="center" text="middle text box" />
<text name="block3" style="textbox" height="fit" valign="bottom" text="bottom text box" />
</panel>
</main>

</wire>


I will make sure we get that put in if it is missing in places. Some attributes have no defaults and simply will not work, but there are some that default as "no" unless you label them as "yes" and so on and so on.

Sorry if this has been a frustation to you. Hopefully we will address this soon.

Thanks.

When you use "fit" as your value for the height attribute in a text object tag, essentially what is happening is the space that the text tag is allowing to display the value from the "text" attribute in the text object will be sized to the height needed to fit all the text you have entered. by default your text will be horizontally centered, if it looks like you have a height of zero, you may need to look at the size of the text tags parent or vertical align your text differently.

This will actually get fixed in the new version that has been submitted to the store already.

Here is what the new design will look like:

This issue should be fixed now.

I have confirmed that to be the case. I am having someone look into this as we speak.

This issue has been resolved. Let me know if you have any further issues with the orientation.

It looks like the current version of Conduit has some issues dealing with stored preferences for facebook and twitter. In the next version of Conduit preferences will be stored on the App level and not on the Conduit level like it is now. This new version should be submitted for approval very soon.

A few things you can do to check for a successful post is to create an alert tag and place it at the point in your wire where the post occurs, this will give you an indication that the message is being sent to facebook from your wire. If that occurs then it might be an issue with Facebook accepting the post request temporarily.

You can also consider deleting Conduit from your device and reinstalling it from the App Store. I say this because you could have gotten a sticky preference, which is unfortunately stored on the conduit level and not the individual App level. This will be fixed in the next version that hits the store.

What version of the iOS are you running on your phone? The current minimum support is 4.3.2.

As we continue to make updates to the engine, we have plans to create a new object tag called canvas, that will allow some masking functionality.

This should be headed into our next engine update, so stay tuned on this one!