CustomDialog | 一个万能的通用支持多功能的Dialog

The CustomDialog must have an onAfterClose or something like that, and in that listener you can invoke forceUpdate

It appears that the issue needs fixing on JavaFX's end. In fact, the button bar is simply pushed out of view. There is a relatively decent workaround though. Dialog internally uses a styled GridPane to display header text and graphics, so I simply replicated that using an external GridPane and instead bound to the textProperty() of a Label.

You can make the method static, and call the method with the class name, Like this:

Return a value from your checkToken function that indicates whether the navigator should push or not. For example you can return null in case of an error or simply return boolean where true means push or false means don't push (or you could return the error string and check it inside onTap if you prefer that).

Let's assume you choose to return null if the navigator shouldn't push the page, then you can do this:

The data type of pressedAction should be Function. And since it should take a parameter you can use Function(dynamic action)

I wrote an example here:

Using a gradient to display two distinct color is generally not a good idea (the very concept of gradient is to show, well, gradients...).

It is possible by setting very narrow limits between colors:

Root cause

You got NPE because onAttach() callback is called when the fragment is attached to its host/activity. The context param is the activity itseft, not the FragmentMain.

Solution

Step 1: When you click on the open dialog button in FragmentMain.

How you access state in a dialog will depend on the scope of the state.

If the state is scoped to the dialog then you should be using dialog state. More specifically, you should be using the state property of the dialog's associated dialog instance. There's some discussion of that in a recent answer here: Dialogs keep their variable values in new conversation in MS BotFramework v4

(Read about dialog instances here). Anything you want your dialog to keep track of, you should put in the associated dialog instance's state object, and the best place to see examples of how to do that is in the SDK source code itself. For example, you can see how a waterfall dialog keeps track of things like its custom values and what step it's on:

Pagination will gives you the data related to the page, for example page one will returns data from 1 to 20, page two from 21 to 40. so you have to add data of page 2 to existed data from page 1. but in your case you are calling search_result_list.clear(); this will erase the old data and put only the new data into the list.