0

openFullscreen

A useful function, but if a button is used to execute this, once in Fullscreen mode, the button is still there, but of course now effectively useless.

Is there a way to detect whether in Fullscreen mode or not, so the button can be hidden or displayed as appropriate?

6 replies

null
    • Ninox partner
    • RoSoft_Steven.1
    • 1 yr ago
    • Reported - view

    You can use a Yes/No field (let's say FULLSCREEN, i use a toggle slider) and put this in the trigger after update:

    if FULLSCREEN then openFullscreen(this) else closeFullscreen() end

    The setting 'Binding' should be 'Global variabele in memory (browser)'

    • UKenGB
    • 1 yr ago
    • Reported - view

    Thanks, I'm doing something like that, but was hoping Ninox had a function to determine if in Fullscreen mode.

    I have however come across a problem with using openFullscreen.

    I have a large multiline text field into which I am writing some data and the button that does that ends with openFullscreen(…) to expand to fullscreen and show as much data in that field as possible. Works fine.

    However, I have another button that clears that field and ends in closeFullscreen(), but which does not always work.

    If I create the data and it expands and then I press the clear button, it closes as it should. If however I do anything else within that Fullscreen view, (like pressing the create button again), then when I press the clear button, it does clear the field, but does NOT close Fullscreen view. It seems that any other action while in Fullscreen mode makes Ninox forget it's in Fullscreen mode and so closeFullscreen() does nothing.

    This is not a large or complicated table and the actions are simple, but as far as I can tell, Ninox is not working as it should. If in Fullscreen mode, then issuing the closeFullscreen() command MUST do that. It should not depend on what you did while in Fullscreen mode.

    Bug?

      • Ninox partner
      • RoSoft_Steven.1
      • 1 yr ago
      • Reported - view

      UKenGB

      Yeah, seems like a bug. It's like the fullscreen is connected to the record where you opened the fullscreen, and with the creation of a new record in that fullscreen, it loses the connection to the current for closing.

      Maybe try, if you trigger the yes/no-field FULLSCREEN (as above) with the buttons? using FULLSCREEN := true or false  and not the closeFullscreen() command in your 2 buttons ?

      • UKenGB
      • 1 yr ago
      • Reported - view

      RoSoft_Steven It's not a major problem. I just have to use the X in the top left to close Fullscreen. However, there's no point in having a command if it doesn't work, so Ninox should flag this to be done.

      • Alan_Cooke
      • 1 yr ago
      • Reported - view

      UKenGB When in fullScreen the form/view is Modal, meaning it takes priority over everything.  A word of caution DO NOT try fullScreen in either of the two Tab Trigger before view or Trigger after hide.  I tried it on Options - Trigger after open and - big problems!!

      • UKenGB
      • 1 yr ago
      • Reported - view

      Alan Cooke Yes I discovered that too.

Login to reply

Content aside

  • 1 yr agoLast active
  • 6Replies
  • 151Views
  • 3 Following