FoxInCloud
Problems with form.closable=.T.
Gravatar is a globally recognized avatar based on your email address. Problems with form.closable=.T.
  Michele
  thn@foxincloud.com
  Oct 24, 2014 @ 02:48am
I have some forms where, even if i set Closable = .T., when the form is opened it hasn't the close button in the right corner of the form and obviously i can't close it....

Gravatar is a globally recognized avatar based on your email address. Re: Problems with form.closable=.T.
  FoxInCloud Support - Thierry N.
  Michele
  Oct 24, 2014 @ 02:52am
is the form modal?


I have some forms where, even if i set Closable = .T., when the form is opened it hasn't the close button in the right corner of the form and obviously i can't close it....


-- thn (FoxInCloud)

Gravatar is a globally recognized avatar based on your email address. Re: Problems with form.closable=.T.
  Michele
  Thierry Nivelet (FoxInCloud)
  Oct 24, 2014 @ 02:56am
it is not modal (as form property) but when i call it i set a "callback" method.....But i have to use that button even in this cases....


is the form modal?


I have some forms where, even if i set Closable = .T., when the form is opened it hasn't the close button in the right corner of the form and obviously i can't close it....


Gravatar is a globally recognized avatar based on your email address. Re: Problems with form.closable=.T.
  FoxInCloud Support - Thierry N.
  Michele
  Oct 24, 2014 @ 03:22am
When you set the 2nd parameter of thisForm.wForm(form, callback method), the form is de facto modal.

So far modal form never have a close button because we'd need to implement the click on this close button (from a 3rd party library) to fire the call-back method on the server.
This implementation is a bit complex because it requires that we differentiate whether form.QueryUnload() has code or not.

Just tell me how complex it it for you to add a 'close' button on this/these form(s) maybe in the parent class. Then we'll measure what is more complex/risky: add a 'close' button in the app or add the call-back support on the HTML form close button.


it is not modal (as form property) but when i call it i set a "callback" method.....But i have to use that button even in this cases....


is the form modal?


I have some forms where, even if i set Closable = .T., when the form is opened it hasn't the close button in the right corner of the form and obviously i can't close it....



Gravatar is a globally recognized avatar based on your email address. Re: Problems with form.closable=.T.
  Michele
  Thierry Nivelet (FoxInCloud)
  Oct 24, 2014 @ 03:27am
I'll see to modify my app, but i have some situations where the only button in the form is the close button and it is not so beauty....but i can accept it...


When you set the 2nd parameter of thisForm.wForm(form, callback method), the form is de facto modal.

So far modal form never have a close button because we'd need to implement the click on this close button (from a 3rd party library) to fire the call-back method on the server.
This implementation is a bit complex because it requires that we differentiate whether form.QueryUnload() has code or not.

Just tell me how complex it it for you to add a 'close' button on this/these form(s) maybe in the parent class. Then we'll measure what is more complex/risky: add a 'close' button in the app or add the call-back support on the HTML form close button.


it is not modal (as form property) but when i call it i set a "callback" method.....But i have to use that button even in this cases....


is the form modal?


I have some forms where, even if i set Closable = .T., when the form is opened it hasn't the close button in the right corner of the form and obviously i can't close it....




Gravatar is a globally recognized avatar based on your email address. Re: Problems with form.closable=.T.
  FoxInCloud Support - Thierry N.
  Michele
  Oct 24, 2014 @ 03:52am
OK we've added an entry to our roadmap.
It's a quite complex change requiring in-depth analysis to carefully identify the possible impacts.
That's why I can't provide a hotfix as we often do, like we did yesterday for the grid row CSS issue raised by Tuvia.

In fact - it's both funny and normal - you users raise on-by-one all issues that we know aren't clear in FoxinCloud - complex things that we've left aside thinking they were 'minor cases' that 'should not happen so often' - and of course they do happen in real life!
{OK, that's a tweet <s>}


I'll see to modify my app, but i have some situations where the only button in the form is the close button and it is not so beauty....but i can accept it...


When you set the 2nd parameter of thisForm.wForm(form, callback method), the form is de facto modal.

So far modal form never have a close button because we'd need to implement the click on this close button (from a 3rd party library) to fire the call-back method on the server.
This implementation is a bit complex because it requires that we differentiate whether form.QueryUnload() has code or not.

Just tell me how complex it it for you to add a 'close' button on this/these form(s) maybe in the parent class. Then we'll measure what is more complex/risky: add a 'close' button in the app or add the call-back support on the HTML form close button.


it is not modal (as form property) but when i call it i set a "callback" method.....But i have to use that button even in this cases....


is the form modal?


I have some forms where, even if i set Closable = .T., when the form is opened it hasn't the close button in the right corner of the form and obviously i can't close it....






-- thn (FoxInCloud)

© 1996-2024