# Popup {#popup}
-![ ](../assets/img/popup/popup-example.png) ![ ](./popup-example.png)
+![ ](./popup-example.png)
## Description {#popupdescription}
- Content
- Footer
-![ ](../assets/img/popup/popup-fields.png) ![ ](./popup-fields.png)
+![ ](./popup-fields.png)
Each field can contain any Actor.
Note: All actor properties are optional, allowing any combination of content areas.
Example: Image only popup (using the content field):
-![ ](../assets/img/popup/popup-image-content.png) ![ ](./popup-image-content.png)
+![ ](./popup-image-content.png)
### Example content: {#popupfieldexample}
### Example: {#popuptoastexample}
-![ ](../assets/img/popup/popup-toast.png) ![ ](./popup-toast.png)
+![ ](./popup-toast.png)
Here is the code to produce the above example:
The ConfirmationPopup will dynamically make the connection between the signalling control, and your signal handler.
-This allows connection of signals within both C++, JSON and JavaScript APIs.
+This allows connection of signals within both C++ APIs and JSON.
If more manual control or customizable layout is needed, then it is recommended to use the Popup widget directly for full control.
The JSON code example at the bottom of this document uses the ConfirmationPopup to allow signal connection from within the JSON description.
~~~
-@class _Guide_Popup
*/