Show works, Hide doesn't

[GGandhi]

Re: Show works, Hide doesn't

here is the first one
https://www.screencast.com/t/hgz1DkyLe
wait for the next with one repeating section

[GGandhi]

Re: Show works, Hide doesn't

this is with one repeating section
https://www.screencast.com/t/ODRuiAJjiQe
wait for two repeating sections.

[GGandhi]

Re: Show works, Hide doesn't

here is one with two repeating sections and static text and placeholder text.
https://www.screencast.com/t/p7UzeaAixik

ask me any questions or doubts. i will try to explain.
i can post one where you populate the dialog too if you wish.

[GGandhi]

Re: Show works, Hide doesn't

here is one to populate the dialog with id selected ( i did not enforce starting number to be 1)
https://www.screencast.com/t/bfz7DDar5gJ

[Ronald Anusiewicz]

Re: Show works, Hide doesn't

I've watched your screencast twice each. Thank you for taking the time to do them. Let me digest what I just learned and I will go back and update some of my UX components.



While I was writing this message, you posted another. Thank you so much!

[Ronald Anusiewicz]

Re: Show works, Hide doesn't

OK, I do have one question. On the desktop side, it was always recommended that the key be an auto increment Character field.
I have noticed that you are using a numeric field. Do you think that matters? My tables are part of a large desktop application running
for the last 15 years and the key is character.

[GGandhi]

Re: Show works, Hide doesn't

see one line is better than three pages code.
you paid ton of money for alpha for you not to write so much code. (on the web side you will end up writing some but not for little things like saving data)
i saw you wrote in your code converting data using W_UPPER function. if you figure that out how use it in the new way of doing things, fine. if not post back i will show you how.

[GGandhi]

Re: Show works, Hide doesn't

for one thing autoincrement field being character is not good, especially i see work with MySql.
but if you must, then it is okay you can continue to use it in the desktop side but if i were you, i will change that soon.

[GGandhi]

Re: Show works, Hide doesn't

but i don't want to leave an impression character autoincrement will not work on the web side, that is not true. just not preferable.(especially in any flavor of sql servers)

[GGandhi]

Re: Show works, Hide doesn't

OK, I do have one question. On the desktop side, it was always recommended that the key be an auto increment Character field.
I have noticed that you are using a numeric field. Do you think that matters? My tables are part of a large desktop application running
for the last 15 years and the key is character.

no it does not matter.

[GGandhi]

Re: Show works, Hide doesn't

function tempfunction_63920708_be5a_4ba9_9664_18b05b5047e3() {
{dialog.object}.submit();
}

function tempfunction_8bc7cadc_0b70_49cc_a139_218f75ad583a() {
var data = {dialog.object}.getValue('PTRANSNO');
{dialog.object}.populateControlsFromTable(data,false,'','<Default>','<Default>',{"showWaitMessage": false});
}

function tempfunction_1bb6acf2_9abd_419e_8453_1fd1a829af24() {
{dialog.object}.fadeOutMessage('{dialog.componentname}.V.R1.MESSAGE','Saved Changes',3000,true);
}

A5.executeThisThenThat(tempfunction_63920708_be5a_4ba9_9664_18b05b5047e3,tempfunction_8bc7cadc_0b70_49cc_a139_218f75ad583a,tempfunction_1bb6acf2_9abd_419e_8453_1fd1a829af24);

when you have a chance please explain the need for the second and third functions for dialog object submit.

[Ronald Anusiewicz]

Re: Show works, Hide doesn't

You have to remember that I had been working on the Desktop side since 1990 starting with Alpha 4. So my thought process is what I am use to doing. The WEB side is like learning to walk all over again, at least for me. There are so many choices and while there is help and videos, there is so much to learn, and unlearn.

Regarding Function 2: I was opening a UX from a button on another UX. I was using Action Javascript. Under Target Window, Sub-theme, I selected Panel. What was happening was after I made a change and saved it, I couldn't close the UX. A message would pop up stating the UX was dirty and to cancel or save my changes. Not sure if this is a bug but function 2 would clear that message and allow me to close the UX. I have since learned to leave the Sub-theme blank and the problem has gone away.

Function 3 just goes back to what I'm use to doing on the desktop. Coding one step at a time. Yes, now I know to use the genie's. Just going through the learning process.

Thanks

[GGandhi]

Re: Show works, Hide doesn't

Regarding Function 2: I was opening a UX from a button on another UX. I was using Action Javascript. Under Target Window, Sub-theme, I selected Panel. What was happening was after I made a change and saved it, I couldn't close the UX. A message would pop up stating the UX was dirty and to cancel or save my changes. Not sure if this is a bug but function 2 would clear that message and allow me to close the UX. I have since learned to leave the Sub-theme blank and the problem has gone away.

i think this is because you are using your own save data function, if you use alpha actionjavascript this may not happen, try it and see if that works. obviously i cannot do the testing.

Function 3 just goes back to what I'm use to doing on the desktop. Coding one step at a time. Yes, now I know to use the genie's. Just going through the learning process.

i do understand where you are coming from and the web side is different. but remember, the people using the system will not be locked into the screen as in desktop. they will move around ( more than you think or want to know ) the best way is to send a message to the browser and display it till they comeback to read the alert box and acknowledge. the fade out message will work if they are looking at the screen all the time. but if they move away and come back and the fade out message comes and fades away no one will ever know, and they will do some stupid stuff and put the blame on you.
if you need to know how to repopulate the ux and send an alert message upon saving the data let me know i will post an example.
see if that is more desirable.
in the meantime good luck, trust me web is learning in a long way but it is fun.(things change everyday, every minute)

[Ronald Anusiewicz]

Re: Show works, Hide doesn't

i think this is because you are using your own save data function, if you use alpha actionjavascript this may not happen, try it and see if that works.

I'm pretty sure I tried this again after changing from my original method to your method with the same results. Interestingly, I had to create a new action script as the sub-theme panel seemed to be locked in to the original even though the field was blank.

The alert is good for the once in a while user. In my case, I have people with stacks of paper and key strokes and mouse clicks count. Now that the form reverts to being not dirty and the buttons gray out correctly, the fade out message should work fine even if they don't look at it.

[GGandhi]

Re: Show works, Hide doesn't

it is definitely okay with me, however

A5.executeThisThenThat(tempfunction_63920708_be5a_4ba9_9664_18b05b5047e3,tempfunction_8bc7cadc_0b70_49cc_a139_218f75ad583a,tempfunction_1bb6acf2_9abd_419e_8453_1fd1a829af24);

this part of the code is designed to combat asynchronous nature of AJAX to emit the action sequentially, as far as i know this will fire regardless of the earlier functions completed or not ( no error checking ).
in desktop the terminal is tethered to the server all the time, on the web side please remember that it is disconnected all the time, only connected when a communication is needed.
so when the dialog submit action is fired and before successful completion ( server may go down or disappear ), the second action that depends on the first will fire and probably fail, and the third one will fire and the message will fade out informing that the record was saved when that is not the case.
if i were you i would use error checking and only when it succeeds i will fire the second and third functions, not without verification.

if i am pestering you, sorry. if you have already taken the precaution, then well and good.
as always good luck with whatever you do.