Hi team, 
long time no see but here I'm with another problem which is properly caused by not understanding the API.

I use the version:

implementation("com.microsoft.device.dualscreen:twopanelayout:1.0.1-alpha06")

My code
Based on the tutorial, I tried to get my TwoPaneLayoutNav working.

class MainActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContent {
            val navController = rememberNavController()

            TwoPaneLayoutNav(
                navController = navController,
                singlePaneStartDestination = "regions",
                pane1StartDestination = "regions",
                pane2StartDestination = "regions"
            ) {
                composable("regions") {
                    RegionsScreen(
                        navigateToRegion = { id -> navController.navigate("regions/${id}")}
                    )
                }
                composable("regions/{id}") { backStackEntry ->
                    val id = backStackEntry.arguments?.getString("id")
                    RegionScreen(regionId = id ?: "A")
                }
            }
        }
    }
}

*The problem *
But as soon as I span the app across both screens, the app crashes with the following error:

java.lang.IllegalArgumentException: Invalid route regions, not present in list of routes []

I tried not just regions but regions/a, too. Both does not work. If I introduce another path like "test" is also does not work. In single screen mode, everything works as expected.

Thanks for your help!

The current pane should not be changed by the navigation methods when both panes are showing

I have a Scaffold in the MainActivity which shows a NavigatioRail or a Bottom Bar component depending on whether the app is spanned or it's a foldable Expanded device or it's a Compact/Medium display (i just used WindowsState as stated in some other Windows example projects). The NavigationRail is wrapped as a Component into a Row layout into the Scaffold and I noticed that when it's laid out Horizontally, the first pane just gets cut out at the very end whilst the second pane is laid out correctly.
One more thing: I didn't assign a weight to none of the 2 panes.
Could you please fix this? Thanks

🐛 Describe the bug

The DragAndDrop API in its current form is not possible to use.

⚠️ Current behavior

Functions have dubious naming:

• DragContainer and DropContainer sound like counterparts but they are not. DragTarget is the current counterpart for DropContainer. Try to use them by their current naming and it doesn't even layout correctly - DragContainer does something to break the component being added to layouts.
• DragTarget makes no sense because "target" refers to where you are dropping the thing. Usually we refer to the place where you start the operation as the "drag source".
• What DragContainer actually appears to be for is... just drawing the overlay? So maybe a good name would be DragAndDropOverlay or something to that effect.

Next issue is, the MIME type system isn't flexible enough to actually use, real data transfer pretty much lets you have anything you want.

Last issue is major, the current API requires the draggable data to be constructed in order to declare the drag target. You don't want to eagerly instantiate the draggable data for every item in the application. That's how you make an application run out of memory. Instead, there should be some kind of callback to create the draggable data which would be one of the parameters for the drag source.

I also expected some kind of method for consuming the thing when it was dropped but I couldn't find it at all. Actually I'd expect two callbacks. One for the drop target to inform it that some data has been dropped, and another for the drag source to inform it that the data has been dragged out (at the time when the drop happens, though, not as soon as it's picked up, otherwise when the user cancels the drag by hitting Escape, they will find out they have nothing left).

So all up I don't think this library is usable to implement drag and drop, but it does give good, solid examples of how the different bits have to be fit together to make drag and drop work, which is helpful anyway.

✔️ Expected behavior

The library can be used without hassle, the API makes sense and things generally work.

🪜 Steps to reproduce

📷 Screenshots

📱 Tech info

• Name of the library:
• Library/sample version:
• Device/emulator version/model:
• OS:

🐛 Describe the bug

I found that after updating the navigation-compose dependency to 2.6.0 the navigateToPane2() function crashes with the following log:

FATAL EXCEPTION: main Process: com.xxx.xxx, PID: 12507 java.lang.NoSuchMethodError: No virtual method getBackQueue()Lkotlin/collections/ArrayDeque; in class Landroidx/navigation/NavHostController; or its super classes (declaration of 'androidx.navigation.NavHostController' appears in /data/app/~~phM2qZ5vae1iOopB_iXCPg==/com.xxx.xxx-QMpXgWBhbZ6qhfai2lCApw==/base.apk!classes15.dex) at com.microsoft.device.dualscreen.twopanelayout.twopanelayout.TwoPaneLayoutCoreKt$SinglePaneContainer$3.invoke(TwoPaneLayoutCore.kt:72) at com.microsoft.device.dualscreen.twopanelayout.twopanelayout.TwoPaneLayoutCoreKt$SinglePaneContainer$3.invoke(TwoPaneLayoutCore.kt:71)

⚠️ Current behavior

FATAL EXCEPTION: main Process: com.xxx.xxx, PID: 12507 java.lang.NoSuchMethodError: No virtual method getBackQueue()Lkotlin/collections/ArrayDeque; in class Landroidx/navigation/NavHostController; or its super classes (declaration of 'androidx.navigation.NavHostController' appears in /data/app/~~phM2qZ5vae1iOopB_iXCPg==/com.xxx.xxx-QMpXgWBhbZ6qhfai2lCApw==/base.apk!classes15.dex) at com.microsoft.device.dualscreen.twopanelayout.twopanelayout.TwoPaneLayoutCoreKt$SinglePaneContainer$3.invoke(TwoPaneLayoutCore.kt:72) at com.microsoft.device.dualscreen.twopanelayout.twopanelayout.TwoPaneLayoutCoreKt$SinglePaneContainer$3.invoke(TwoPaneLayoutCore.kt:71)

✔️ Expected behavior

No crash

🪜 Steps to reproduce

1. Add the following dependencies
   androidx.navigation:navigation-compose:2.6.0
com.microsoft.device.dualscreen:twopanelayout:1.0.1-alpha07
2. Use the function navigateToPane2()
3. App crashes

📱 Tech info

• Name of the library: com.microsoft.device.dualscreen:twopanelayout
• Library/App version: 1.0.1-alpha07
• Device/emulator version/model: Pixel 6
• OS: SDK 34