How to handle the windows arrow for backwards

Scriptcase 9 General
#1

How to handle the windows arrow for backwards. I have an application wit grid and form.
When I push the “back arrow” on the top of my screen (chrome) the application stops / crash.
How to solve this. With the button in the application it is ok. But there are customers who use the windows arrow an then phone me.

#2

I use this code on aplicationinit on menu app for example:
?>

history.pushState(null, document.title, location.href);
window.addEventListener('popstate', function (event)
{
  history.pushState(null, document.title, location.href);
});
</script>
<?php
#3

Hi, thanks gbillot3 for the contribution. On the other hand, the claim to SC should be fine and it should work and go back without writing any additional code.

#4

Hi @daguard , that’s not going to happen. It is a recurring problem as old as Sriptcase.

#5

That’s why I often wonder whether to continue with SC or start using other tools for new projects. Like Laravel, for example. What is your opinion?

#6

That is very personal. SC is a great tool for those with little/medium knowledge.
They should fix all the bugs before they keep innovating to sell.
Also before releasing a new version they should take more time for testing.
I understand that there are a lot of things to test and it is easier to release the version and let the users test and find the problems. But it is unprofessional to leave the users without being able to move forward with their developments.
Over time you learn that you have to wait for new versions to mature. In my case I haven’t upgraded to 9.11 yet and I see that I saved myself a lot of headaches.
The ideal is not to depend on anyone for developments but that is difficult.
Have a nice day!

#7

I don’t think Laravel is comparable with Scriptcase as it is a different development approach. Nothing wrong, but different. I agree with gbillot3. It is personal. I switched to an alternative and abandoned SC personally. Not business-wise, as we (University of Groningen) have a massive code base, which you can’t simply migrate into something else. But I second the arguments as I used to be involved with SC, since version 5 dot something. Over the years, I’ve seen many similar comments in regards of testing, support, quality, focus on whistles and bells instead of fixing issues, etc. I got a more or less hate/love situation. For the purposes of the University it works fine as we stick to administrative applications and do nothing fancy. But over the years I had many, many issues of things that worked, than not worked, worked again, new bug etc.I was tired of the same old story over and over again.

#8

Hi aducom. This sums it all up: Precisely the fact that an SC application works today and after an update it doesn’t work well and/or new problems appear is what’s wearing me down.

I also have to keep going because everything I’ve developed has been updated for more than 10 years.

A change implies starting everything from scratch and it can be unfeasible in terms of time and costs. That’s why I’m thinking about what to do with the new projects.

Can you tell me which alternative you’ve chosen?

Regards.

#9

Yes, but not on this forum. I think it is not ethical to do so as I’m also here as someone trying to help others. But email a.drent at aducom dot com, and I’ll answer you honestly.

#10

I agree with that and I think it’s fine. I also try to help others with some experience I’ve had because I’m still doing this anyway.

#11

same here, it depends on the project. for the most part, I prefer scriptcase for speed :smile: