Yeah, I didn't understand states. Changing from one state to another always unplays the properties and styles set in the previous state. Not a fan of that at all but that explains all my confusion.
On Tue, Jul 8, 2008 at 5:07 PM, dfalling <[EMAIL PROTECTED]> wrote: > I thought I had states down pat until the last few days. > > **States:** > normal state: > - change viewstack to show data renderers > no data state: > - change viewstack to show "no data" error view > fetching data state: > - <empty> > > **Transitions:** > to fetching data state: > - display fetching data view > from fetching data state: > - hide fetching data view > > My problem is that whenever I went into the fetchingData state, it > would properly perform the transitions for that state (showing the > fetching data view), but would also incorrectly perform whatever code > was inside the no data state. It also performed the code in the > fetching data state. > > I created a function to watch the state changes and the no data state > was never being entered, but its properties were definitely being applied. > > I now have it working by doing everything in transitions, but does > anyone know why this problem would happen? I tried to write a small > sample app to demo this problem, but of course it worked fine. > > Thanks > > >
