Alive UX glitches on local preview

Bug Reports
1

Please try to reproduce the steps described in the comments on the code, the local preview viewport is showing several visual glitches when auto reloading an app with any Alive UX component. FYI I’m on Windows 10, Fuse 1.0 build 13426, the glitches occur with Fuse Studio enabled or not, the only solution is to rebuild every time a new component is added to the visual tree

<App>
	<Alive.FallbackTheme />
	<ClientPanel>
		<Alive.DarkTheme />
		<Alive.NavBar Dock="Top">
			<Alive.NavBarTitle Alignment="Center">Alive UX NavBar</Alive.NavBarTitle>
		</Alive.NavBar>
		<ScrollView>
			<StackPanel ItemSpacing="20">
				<Each Count="10">

					<!-- UNCOMMENT THIS BLOCK FIRST AND SAVE TO AUTO RELOAD -->

					<!-- <Rectangle Fill="#AAAAAA" Margin="10">
						<Text Alignment="Center" Margin="10">Classic Card</Text>
					</Rectangle> -->

					<!-- END OF THE 1ST BLOCK -->

					<!-- NOW THE SCROLL VIEW IS FROZEN UNTIL YOU HIT REBUILD ON FUSE STUDIO -->


					<!-- NOW UNCOMMENT THE CARD, DON'T FORGET THE CLOSING TAG, THEN SAVE -->
					<!-- TAKE A LOOK AT THE PREVIEW VIEWPORT, BUT DON'T REBUILD YET -->

					<!-- <Alive.ThemedCard Margin="10">
						<StackPanel>
						<Alive.DarkTheme/>
						<Alive.CardMedia>
							<Alive.Title Alignment="Center" Value="Alive UX Card Title"/>
						</Alive.CardMedia> -->

						<!-- FINALLY ENABLE THE CARD BODY BELOW -->
						<!-- THIS TIME NOTHING HAPPENS, UNTIL REBUILD IS CALLED -->

						<!-- <Alive.CardBody>
							<StackPanel Orientation="Horizontal">
								<Alive.BackButton/>
								<Alive.ActionButton/>
							</StackPanel>
						</Alive.CardBody> -->


						<!-- </StackPanel>
					</Alive.ThemedCard> -->

					<!-- WITHOUT ANY ALIVE.UX COMPONENTS ON THE VISUAL TREE, EVERYTHING WORKS PRETTY SMOOTH -->
					<!-- IT SEEMS THAT MOST GLITCHES OCCUR UPON THE ADDITION OF NEW COMPONENTS TO THE TREE -->
					<!-- SOME PARAMETER CHANGE CAN BE DONE WITHOUT THE GLITCH -->

				</Each>
			</StackPanel>
		</ScrollView>
	</ClientPanel>
</App>
2

Hi! Thanks for the report, apologies for the slow response. This appears to be an issue with setting the FallbackTheme directly on the App tag.

I was able to fix this by wrapping everything in a Panel at the root, like so:

<App>
    <Panel>
        <Alive.FallbackTheme />
        <ClientPanel>
            ...

However, I realize that the docs are telling you to put the FallbackTheme directly on the App, I’ll make sure they are updated accordingly :slight_smile: Not entirely sure about the root cause of this though, I’ll investigate some more and raise a ticket.