locky | Resource locking system using redis

You must remove your NestedScrollView (Nested_Scroll) in your activity layout - you cannot put a vertical RecyclerView within a NestedScrollView.

A NestedScrollView expands every child in the vertical scroll direction to determine the maximum scroll distance. This means that it gives the RecyclerView an infinite height to expand into. This causes RecyclerView to inflate every element, defeating all view recycling and defeating the use of paging - given infinite height, it'll continue to ask Paging for more and more rows to fill the space.

you have the same layoutmanager for both fragments, when you populate your different fragments; the same layoutmanager is called. Which then tries to restore the same position thinking its the same recyclerview, which is kind of a feature when you think about it.

from the docs:

Called when the RecyclerView is ready to restore the state based on a previous RecyclerView. Notice that this might happen after an actual layout, based on how Adapter prefers to restore State. See RecyclerView.Adapter.getStateRestorationPolicy()

which means what we need is not to restore the state which can be done by passing PREVENT to RecyclerView.Adapter.StateRestorationPolicy

solution1: in your fragment B adapter just call adapter.stateRestorationPolicy = PREVENT

solution2: create a different layoutmanager for fragment B in case you want to restore position for something else.

EDIT :: QA :: how can i set the view to be on top (Near Status Bar) :

Well, since you are populating your fragments inside a NestedScrollView you should call NestedScrollView.scrollTo(0, 0); when you navigate to the required fragment probably by waiting on a callback from addOnDestinationChangedListener inside your MainActivity.kt

Change your "showFabs" by this

Kotlin

As of Navigation 2.3.0-alpha02, Navigation has built in support for Returning a result to a previous destination.

This works in two parts, your first fragment (the one wanting to receive the result) would use navController.currentBackStackEntry?.savedStateHandle to get a reference to the SavedStateHandle associated with its NavBackStackEntry in the NavController. Then, it can observe a particular key to get a callback whenever that key changes.

The second fragment (the one delivering the result, i.e., your LogoBottomSheetFragment) would get a reference to that exact same SavedStateHandle by using navController.previousBackStackEntry?.savedStateHandle. When that second fragment calls set on the SavedStateHandle, that result is then made available for the first fragment.

Note that there are some DialogFragment specific considerations to keep in mind - because the previous fragment is RESUMED even when the BottomSheetFragment is being shown, the result will instantly be sent to your first fragment.

Suppose the monitor's parent transform is the body/keyboard of the laptop. Local axes of the parent shown below:

To describe the range of motion you can define a "center of rotation" vector (e.g., grey vector labeled C) that is local to the parent and an angle (e.g., 110 degrees, between each purple vector and the grey vector). For instance:

You're sending the first request to https://api.monkey-locky.com but the URL in the second request is https://api.monkeylocky.com (no dash)

Well if say x = 50 and y = 5 then you have x > y and x > 2*y so there is no contradiction.

But you could add the following to your first if condition:

Another way to describe your issue is that your y-axis goes from 100 (technically, limitY) to 0 when it ought to go from 0 to 100. Therefore, we can slightly change your code to reverse this axis by fully calculating the y percentage, and then subracting it from 100. (ie, 100 - 80 = 20 or 100 - 35 - 65.) This will change the high values into low values and vice versa. Then, if we want to convert from percentage to pixel, we simply subtract it from 100 again to get our original flipped percentage (that you've already done all of the work for.)

The two lines changed are:

Here's the issue, the first time your app adds a document’s on-disk representation to an iCloud (ubiquity) container, the system transfers the entire file or file package to the iCloud server, this task create the document’s metadata first, which includes information such as the document name, modification date, file size, and file type ("wrong" decoded string above) and then transfer the data (file).

In Apple Docs

In iOS, apps must ask the system (either explicitly or implicitly) to download the file. You implicitly download a file by trying to access that file by using methods in the NSFileCoordinator class, or you explicitly download the file by invoking the startDownloadingUbiquitousItemAtURL:error: method in the NSFileManager class

and that's it, after call this methods, file can be read and contents is correct instead of metadata.