DashBoard Maximize button widget made always a reload ?? (sc8)

Scriptcase 9 General
#1

Hi you all,

I certainly did not figure how the maximize button works in the widget header…

Well, I have a GridApp and a linked FormApp, really basic : a grid with the edit button (pencil) on each line to edit the record ion a Form.

Now I made a 50 / 50 two columns dashboard with one widget in each column. I specify that for each widget the Maximize option is ON.
The left widget is linked to the GripApp … run and works as expected

BUT

When the FormApp is called and the widget maximized on or off the widgets refresh and I lost my FormApp returning to the GridApp ! ??

the process is :

1 - Widget maximized or not : GriApp -> FormApp OK
2 - Widget maximized or not : GriApp -> FormApp OK then maximize action -> return to the GridApp automatically

Is that a normal behavior to reload after each maximize action ???
And if so did you know a way, a trick not to reload when maximize action ?

Thanks in advance !

​[edit]
I find an old post talking about same problem as a bug in http://www.scriptcase.net/forum/foru…iginal-content

#2

Hi sorry to be insistent in this forum , Im blocked waiting for the Scriptcase answer too …

I apologize for my English did I have correctly formulate my question ?

The purpose is that in a widget with a grid who open a form the form quit and return automatically to the grid when the Maximize button is clicked . So what ? we are not able to execute a basic Grid->form in a widget ??

Sorry but my current projet is based on some screens including widgets … did I have to go back because of the maximize button who returns automatically from a form to his linked grid ?
any of you have ever encountered such problems ?

#3

I forward here the answer from Sc Ticket :

“[SIZE=15px]I tried the same thing here and it really happens, it’s a Bug. and I already reported it to our Bug’s team. However, in the v9 this is fixed. Have a wonderful day!”[/SIZE]

Hope SC 8.1 will be bug fixed and updated …

#4

next episode …

I made a test under SV V9.0004

  • One dashboard with two widgets with :
    • One Blank App with php echo text
    • a couple Grid + Form on a single MySQL table (batch application)

Even under SC9 , when I edit the record in the form AND maximize the widget the Form is lost and return automatically in the Grid

Netmake tells me this is fixed in SC V9 but unfortunately not …

Did I miss something or totally misunderstand the process ???

#5

Hi herveo,
I am a long time SC user -still in 8.1. I will have to look and see if that behavior happens to me too.

Am I reading it correctly?

  1. You have a grid and form for that grid.
  2. The grid is initially showing in one of your dashboard iframes.
  3. You click on details on the grid and the form opens for editing.
  4. You start doing some editing - but have not saved yet.
  5. You maximize the dashboard iframe so you can see the form better, and the while app reloads and you lost your changes.

Just trying to get the sequence correct before I try it.

I just did some quick googling on this issue in general. It looks like some browsers have differences on how they implement the iframe and javascript related to maximizing. Just a shoot in the dark but maybe if you tried on three browsers you might find different behaviors. Not a ‘solution’ but good to know anyway. Not sure how much SC staff test across browsers.

One thing I have done with dashboards that might help:

  1. I will generate a grid and form for editing.
  2. I will make a copy of the grid and actually make a special grid that is crafted to look really good in the dashboard.
  3. Put the simplified grid in the dashboard container.
  4. Add a single button on that simple grid called ‘edit’. Link that button to the original grid.
  5. make sure that link opens the original grid and form in the main iframe of the application, so that it is big and easy to read and use.
    This just gives you better control of how the dashboard looks. I have used it when using a grid to monitor user activity in the context of a administrator dash.
    It also helps counteract the bad effect that an auto refresh cycle causes. It you have that set to refresh the grid every 30 seconds, as I do when monitoring something, then the auto-refresh might mess up my editing if it were in the dashboard container.

Anyway, hope that gives you some ideas :slight_smile:
Peace,
Jamie

#6

Hi Jamie,

Thanks a lot for your reply.

Your description of the problem is good , and I have to admit far clearer as mine :o

I test the same behavior under last versions of Chrome, Firefox and Safari. Scriptcase assistance wrote me in a ticket that they reproduce the same behavior too but I don’t know with witch browser …

I did not understand the second term of your message
1 - Grid + From
2 - Crafted grid with an edit button linked to the original grid
3 - ? classical process ? grid -> form for editing in the main iframe

I Apologize but don?t understand Crafted grid -> grid -> form. Two grids ?

Have a nice day

Herve

#7

Hi Herve,
What I mean is that I make a special simplified grid for display in the dashboard. You can put any grid (or app) into a dashboard, but often you do not need all the columns and buttons, etc. Too many things like that make the scrollbars appear or just make the grid to ‘busy’ looking.

The simplified grid with fewer columns can then have a button that links it to open the other full grid (with its form for editing) into the parent frame. So in other words, if you click that button, a full screen grid with more columns and all buttons and features opens up. The form can then be used to edit the details of each record, without concern that the refresh of the dashboard will reload or erase the data.

Hope that helps,
Jamie

#8

Confirmed today in SCv9.0005 that when you have a dashboard and put anything inside it, when that widget is maximized in size, it reloads the app inside.

I think 8.1 did the same. This is in Chrome, but did not try other browsers.

#9

Jamie -> yes I test myself after upgrade to SCv9.0005 same results with different browsers under OS X and Win10. Netmake wrote me in a ticket it’s a bug …