Author Topic: EA Runs the wrong Jscript  (Read 4955 times)

localhro2

  • EA Novice
  • *
  • Posts: 12
  • Karma: +0/-0
    • View Profile
EA Runs the wrong Jscript
« on: April 01, 2016, 07:06:24 am »
I have a weird script issue that appears every now and then.

When I run the a JScript from a diagram it tries to run a different JScript in the same folder instead. This behavior continues until I restart EA. Then, the correct selected JScript will run normally for a while, but the problem will randomly start back up.

Thanks,

Sean

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +396/-301
  • I'm no guru at all
    • View Profile
Re: EA Runs the wrong Jscript
« Reply #1 on: April 01, 2016, 10:13:24 am »
What do you mean by "the wrong"?

q.

localhro2

  • EA Novice
  • *
  • Posts: 12
  • Karma: +0/-0
    • View Profile
Re: EA Runs the wrong Jscript
« Reply #2 on: April 05, 2016, 12:40:18 am »
So say I have three in diagram scripts A, B, & C. When I run Script A, Script B runs instead. Or When I run Script C, Script A runs instead. Totally random and the only way to fix it is to restart EA.

Any ideas?

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +396/-301
  • I'm no guru at all
    • View Profile
Re: EA Runs the wrong Jscript
« Reply #3 on: April 05, 2016, 01:14:47 am »
You should contact Sparx support via mail / send a bug report (link bottom of this page).

q.

fp123

  • EA User
  • **
  • Posts: 28
  • Karma: +0/-0
    • View Profile
Re: EA Runs the wrong Jscript
« Reply #4 on: September 12, 2019, 10:08:38 pm »
I've got the same problem, but with different EA versions.
Yesterday a colleague asked me about a scipt that was always working in a different way than expected in his EA V.13. I tried it on my pc and experienced the same. I called the script via context menu of a package in the project browser but EA always runs the script that is shown above (in the context menu) the one i wanted to run.

Restarting EA get's it to execute the right one again. We've tried EA V.13 V.14 and V.15 but with the same result.
Is this maybe an issue caused by calling a script from another? We use "!INC scriptfolder.scriptname" to call the one that shall be executed from inside anoter script.
« Last Edit: September 12, 2019, 10:12:49 pm by fp123 »

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13283
  • Karma: +556/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: EA Runs the wrong Jscript
« Reply #5 on: September 12, 2019, 10:50:16 pm »
I've written hundreds of scripts, but I never experienced this behavior.
I use VBScript though, so that might make a difference.

Geert

fp123

  • EA User
  • **
  • Posts: 28
  • Karma: +0/-0
    • View Profile
Re: EA Runs the wrong Jscript
« Reply #6 on: September 13, 2019, 12:09:43 am »
Hi Geert,
do you also call other scripts from within a script? At the moment, I think this could be a possible cause for the problem, because it has only happened until now, when we're not calling them directly.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13283
  • Karma: +556/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: EA Runs the wrong Jscript
« Reply #7 on: September 13, 2019, 03:21:33 am »
Hi Geert,
do you also call other scripts from within a script? At the moment, I think this could be a possible cause for the problem, because it has only happened until now, when we're not calling them directly.
Yes, quit a lot even.
I have build a bit of a framework with a whole set of supporting scripts for all kind of stuff.
A typical script would of mine would include at least 30 other scripts (indirectly)

Geert

Sunshine

  • EA Practitioner
  • ***
  • Posts: 1311
  • Karma: +120/-10
  • Its the results that count
    • View Profile
Re: EA Runs the wrong Jscript
« Reply #8 on: September 13, 2019, 07:15:59 am »
Weird, Similarly to Geert, I've written quite a few scripts using JScript and not experienced that sort of thing before.
Maybe share some details on your environment set up and versions might help.
Do let us know when you find the cause.
Happy to help
:)