Hello Derek
Thanks again for your detective work. I was also just testing with only a window so no analysis or variable to encourage the other looper options to appear. I suppose that a message or two from PCSoft on the looper creation screen to explain why the options were unavailable or simply remove or grey them out would have been a better choice.
I think you were right though in nominating the "gallery control" as not quite a GOLD release is correct.
The "control is merely a looper EXAMPLE masquerading as a control. I refuse to acknowledge it as a real control.
The help doesn't show anything about it if set to only show the current product (Windev) but it is touted as being a new control for Windev in the "New Features" .
The "Pager" and three buttons (Favourites,Comment,Share) options shown in the help as being available in the gallery "Control" are not available in the Windev version, presumably they are in the Webdev implementation.
Furthermore there is actually a Windev example in the examples. This example is obviously the development for the final "Gallery "Control" and in Windev is a better option that the final looper control.
(PCSoft must have been quite keen to get the new features count up to add in the use of an unfinished, half baked example as a new "control".)
It is a bit scary that the example presents as a Windev Example yet it has a button with code that executes OpenMobileWindow() which I thought wouldn't work in Windev and should have been Open Child() but it does work in the Windev example and according to the help is available for Windev.
The help graphic icons indicate that "OpenMobileWindow" is NOT available for Webdev but the words in the help say that it is available for Webdev for V24
It looks like PCSoft approach is to try and line up similar functions to operate the same across the three products regardless of the actual command verb used to call them.
e.g. in an application, a call to OpenChild() will function as that command when running in a Windows environment, as OpenMobileWindow() if the same app is running on a mobile and as "<Page> Display" when running in Webdev.
I think this mixing and matching of the three environments is going to be painfull for the next few iterations until it settles down.
I suppose for PCSoft this is no different to what they do now when a command is interpreted the same whether it is coded in French, English, or Chinese.
Regards
Al