Compose
3 TopicsHow do I allow a user to trigger a task module from an adaptive card in the compose area?
I have a teams bot which responds to search queries via a messaging extensions and allows the user to embed card responses in messages and teams. I have reworked it from making use of thumbnail cards to make use of adaptive cards to leverage the ability to trigger Task modules from them so that I can make a popup web view appear when the user clicks the button. This all works fine while the user is clicking the button on the card after it has been posted as a chat or channel reply. The issue is that while the card is still in either the command bar or the compose window, prior to the user copying it or posting their message, the button which triggers the task module does not work. It is also worth noting that the other buttons present on the card which are AdaptiveOpenUrlActions work as expected in both the compose window and the posted message. This is the C# code I am using to add the button to my Adaptive Card: actions.Add(new AdaptiveSubmitAction() { Title = "View", Data = new PreviewTaskModel() { DocumentId = result.Metadata.Id, ContentSourceId = result.Metadata.ContentSourceId } }); My question is: Is this intended functionality? If so does making use of DeepLinking work around this issue?Solved2.8KViews0likes11CommentsCannot find import com.microsoft.device.dualscreen.windowstate.WindowState
Hi team, this might be a noob question but I try to get started using Compose, the Surface SDK and your Dev blog post "https://devblogs.microsoft.com/surface-duo/jetpack-compose-navigation-rail/". But everything I tried, I cannot import WindowState from com.microsoft.device.dualscreen.windowstate.WindowState. Thanks for helping me out! Minor finding: By the way, If I upgrade the versions number to the newest navigation one, NavigationRail is no longer available. Is this true? My dependencies (Gradle in *.kts style): dependencies { var koin_version = "3.1.5" var navigation_version = "2.4.0-alpha10" var compose_version = "1.1.0-alpha06" // Android implementation "androidx.compose.material:material:" implementation "androidx.navigation:navigation-compose:$navigation_version" implementation 'androidx.core:core-ktx:1.7.0' implementation 'androidx.appcompat:appcompat:1.4.1' implementation "androidx.compose.ui:ui:$compose_version" implementation "androidx.compose.material:material" implementation "androidx.compose.ui:ui-tooling-preview" implementation "androidx.navigation:navigation-compose" implementation 'androidx.lifecycle:lifecycle-runtime-ktx:2.4.0' implementation 'androidx.activity:activity-compose:1.4.0' // Google implementation 'com.google.android.material:material:1.5.0' // JetBrains implementation 'org.jetbrains.kotlinx:kotlinx-coroutines-core:1.6.0' // Flow layout implementation 'com.google.accompanist:accompanist-flowlayout:0.22.0-rc' // Microsoft implementation 'com.microsoft.device.dualscreen:twopanelayout:1.0.0-alpha06' implementation 'com.microsoft.device.dualscreen:windowstate' // Ktor implementation("io.ktor:ktor-client-core:1.6.7") implementation("io.ktor:ktor-client-cio:1.6.7") implementation("io.ktor:ktor-client-serialization:1.6.7") // Koin implementation "io.insert-koin:koin-android:$koin_version" implementation "io.insert-koin:koin-androidx-compose:$koin_version" // Map implementation("com.google.android.libraries.maps:maps:3.1.0-beta") implementation("com.google.maps.android:maps-v3-ktx:2.2.0") implementation("androidx.fragment:fragment-ktx:1.4.0") // Testing testImplementation 'junit:junit:4.+' androidTestImplementation 'androidx.test.ext:junit:1.1.3' androidTestImplementation 'androidx.test.espresso:espresso-core:3.4.0' androidTestImplementation "androidx.compose.ui:ui-test-junit4:$compose_version" debugImplementation "androidx.compose.ui:ui-tooling:$compose_version" }Solved1.4KViews0likes4Comments