You could use the rotate tag to move these lines around in your WIRE. You would probably need to assign xpos and ypos to position them how you want.


<wire>
<main>
<panel name="main" width="100%" height="100%" background="ffffff">
<panel name="ONE" alias="ONE" align="center" valign="center" width="50%" height="5" background="000000" alpha="0"></panel>
<panel name="TWO" width="15%" height="18%" background="ffffff" borderwidth="5" bordercolor="000000" xpos="23%" ypos="21%" onclickup="spin" cornerradius="55"></panel>
</panel>
</main>

<action name="spin" >
<sync>
<rotate time="0" times="1" curve="linear" degrees="45" target="ONE"/>
<alpha value="1" target="ONE" />
</sync>
</action>
</wire>


Of course you could always decide to display this with an image as well.

you can create a line in WIRE by making a panel 1px in width and 100% in height and then making sure your main panels are right next to it.

Can you post a screenshot of what you are trying to achieve?

It is best practice to always put your assign tags at the top of an action, esp. when using a sync. They have the tendency to get overridden otherwise. What was happening to you is that when your replace tag kicked in the assigns were not completing and losing the value from the camera. So to fix this I just made the assigns happen first in your action.

I am not aware of any bugs associated to this. I would love to take a look at your code to see if I can find the issue. you can invite me as a collaborator if you would like (icahill@rarewire.com).

Are you capturing the scanvalue and converting it to a variable before you attempt to use it?


<assign property="var:code" value="[object:nameofcameraalias.scanvalue]" />
<assign property="object:nameofwebalias.url" value="[var:code]" />


In this case, the location datasource is not needed to generate the gps location in your map tag.

Remove the datasource and its references and this should work fine without crashes.

The location datasource is used for objects outside of the map to trigger actions.

Doug,

Thanks for bringing this to our attention. We are currently tracking a few memory issues with Apple Maps in iOS 6.

Yep, that would contribute to an error like that. WIRE doesn't like siblings with the same names.

Well done on the self-correction :)

Ok. This appears to be a bug of sorts. We think that the change to Apple Maps as opposed to Google Maps changed the way the pin disappears when replaced.

I have logged a bug for this issue.

Yeah I noticed this as well. I am going to follow up with dev and possibly log a bug.

Thanks!