Doloro GDK 22 .1.0 Beta
by Tauri Interactive
Demo: Shops inspector

About

The demo demonstrates a complex inspector window that provides access to on-scene Shop instances and on-scene Storages related a certain person by its id.

How to start

  1. Navigate by following path toward scenes collection:
    Doloro-GDK \ Doloro-Inventory-Shops \ Scenes \.
  2. Open Shops Inspector scene.

Before running we recommend you enable Maximize on Play mode of the Game view.

How does it work

Shops declaration

The scene hierarchy has Shops declaration game object. Open it to gen on-scene declarations configs for a storages.

Note that entire Storage Caller components refer to default.shop dynamic resource. Such a storages will be instantiated by using of Shop Default resource instance as entity to rent.
The default features settings will be applied according with features declared over the Storage Caller instance. in case if provided.
In case the feature no exists over the storage entity resource, it will be skipped.

Storages generation

The demo scene implements custom demo scriptStorageDatabaseGenerator to provide you with alternative example to of storage generations.

The component located over Demo services game object.
The script allows continues spawn of storages with a random content.

GUI layout

The entire GUI layout elements located under Canvas game object.
Here you can locate 2 important objects:

  1. Shops Inspector. It's an assembled layout works as the demo window.
  2. Parts. The game object that refers parts used at the Shops Inspector window as children. The elements are disabled and added only to make it more obvious which parts the explorer has built.
Part Purpose
Shops UI Shops Selection Explorer Elements Collection of Storage GUI control represented via ShopGUIElement control.
Displays entire stores loaded to the scene via rented Storage entities.
Shops UI Player Storages Selection Explorer Elements Collection of Storage GUI control.
Displays entire storages loaded to the scene via rented Storage entities related to inspecting owner with id defined at ShopsInspector as playerId.
Exchange Buffer UI Available Displays content of 2 selected Storage instances available to use in transaction.
- Left side receives as source selected player's Storage.
- Right side receives as source selected shop's Storage.
Exchange Buffer UI Reserved Displays content of 2 selected Storage instances reserved by TransactionOrder placed between them.
- Left side receives as source selected player's Storage.
- Right side receives as source selected shop's Storage.
Storages Exchange Explorer Layout that builds following layout parts into common layout:
- Exchange Buffer UI Available
- Exchange Buffer UI Reserved

Not implements any specific features or controls.
Transaction order GUI Standalone Standalone Window that calls when you are selecting ItemGUIElement in any exchange buffer.

Provides TransactionOrderInspector instance that manages visualization of
TransactionService.TransactionOrder content.

Allows to place order by pressing confirmation button or cancel it by closing the window.
Warning
Parts by themselves not works as stand-alone windows and must be consumed with a Shops Inspector component defined as hierarchy (or Virtual UI Hub hierarchy) root. The inspector performs role of behavior provider and manages operation between window parts.

In the demo the component does not require assignation of any child part over component. Entire parts implemented as separated Window instances connected to a solid layout by using of Runtime Workspace features.

During windows instantiation process the parts assigns themselves to a parental Storage Inspector found in virtual hierarchy provided with a Virtual UI Hub established with the Shops Inspector game object with VirtualUIHub component.