topic Re: Interface page navigation in Libraries & objects

Interface page navigation

Bruce — Wed, 24 May 2023 08:05:45 GMT

I'm developing a fairly complex object that will have many pages in the UI. I'm trying to mimic the ArchiCAD door page selection method (to keep it familiar for users) but can't figure out how to get the drop-down page selection working with the PREV and NEXT buttons.

(I've tried to figure out how Graphisoft do it, but have gotten completely lost amongst all their macro calls.)

If I set the UI_CURRENT_PAGE via the drop down selection, the UI_PREV and UI_NEXT don't work, and vice versa.

Any hints?

Thanks

Re: Interface page navigation

Anonymous — Wed, 11 Nov 2015 04:47:39 GMT

If I understand correctly, here's a simple example with reference to the standard macro = "ui_tabcontrol"
You create a parameter = "gs_ui_current_page"
tabTitles - You can also create a parameter or make the array directly in the script interface.

!!!PARAMETERS SCRIPT 
!!! You must create the parameter named=gs_ui_current_page

VALUES "gs_ui_current_page" 1,2,3	

IF GLOB_UI_BUTTON_ID > 2 and GLOB_UI_BUTTON_ID < 2.1 THEN
	PARAMETERS gs_ui_current_page = GLOB_UI_BUTTON_ID - 2
ENDIF

!!! INTERFACE SCRIPT
UI_DIALOG "SL-GDL" ! Your any text

UI_CURRENT_PAGE gs_ui_current_page
UI_PAGE gs_ui_current_page

DIM tabTitles[3]
	tabTitles[1] = " Parameters"
	tabTitles[2] = " Represent"
	tabTitles[3] = " Info"

UI_BUTTON ui_prev, "<<", 295+10,2, 32,21, gs_ui_current_page - 1 !!!! Previous
UI_BUTTON ui_next, ">>", 295+10+33,2, 32,21, gs_ui_current_page + 1 !!! Next page

!!! HEAD
!!! Example without icons
CALL "ui_tabcontrol" parameters	controlType = 1,
		nTabs = 3,
		gs_ui_current_page = gs_ui_current_page,
		tabTitles = tabTitles,
		drawBox = 1

!!! PAGES

  UI_PAGE 1 
  UI_PAGE 2
  UI_PAGE 3

Re: Interface page navigation

Gergely Feher — Wed, 11 Nov 2015 08:51:54 GMT

Her is a sample for handling ui pages: http://gdl.graphisoft.com/tips-and-tricks/how-to-set-up-tabpage-controlling-in-ui/

Re: Interface page navigation

Anonymous — Wed, 11 Nov 2015 10:32:28 GMT

Standard macros is a good thing, but there is always the danger that in a new release of version of the GS change the script (or remove some parameters) so that the element will stop working. Well if this is a basic macro that you give a link CALL "...", but if it happens in other levels? Eg. windows - doors, a large number of macros. Modern elements are so complex and they have a CALL "..." a few times (possibly in a circle inside).

Re: Interface page navigation

Bruce — Wed, 11 Nov 2015 20:48:05 GMT

Thanks guys - a great help. Don't understand it yet, but I'll get there. Ta

Re: Interface page navigation

Bruce — Sat, 14 Nov 2015 02:04:57 GMT

Got it working. Turns out the key was adding the "gs_ui_current_page - / + 1" in the UI_BUTTON command.