On Sat, Apr 10, 2021 at 12:30 PM Felix Schumacher < felix.schumac...@internetallee.de> wrote: > > > Am 10.04.21 um 18:21 schrieb Tong Sun: > > On Sat, Apr 10, 2021 at 6:02 AM Felix Schumacher < > > felix.schumac...@internetallee.de> wrote: > >> > >> Am 10.04.21 um 09:23 schrieb Adrian Sp: > >>> Hi, > >>> > >>> It's an open source project. Just check the code and see how it works > >>> under the hood if you feel comfortable with this. > >> Apart from the sources there are other places, where you might be able > >> to find the good stuff, bugzilla for example ;) > >> > >> https://bz.apache.org/bugzilla/show_bug.cgi?id=64658 > > If you still want to disable the splash screen, there is a patch > >> referenced, that should do that. > > > > Thanks Felix, for your effort in trying to help in the previous case, and > > sent that patch. > > > > Ok, if the option to turn off the splash screen is not acceptable, Felix, > > would you make another PR that it ends in an earlier spot please? > > > > The current situation is that, whenever Jmeter has finished load scripts > > and has found a start up problem, the pop up error windows will be behind > > the splash screen. I don't mind the splash screen normally, but I think > > blocking the error windows is something not intended by design, and should > > be fixed. > > Can you tell us, which error is displayed?
[image: image.png] Moreover, when it happens, It's staying on top of everything, making it difficult for me to work on anything else. [image: image.png] > It seems that there are at least two different problems: > > First, that there is an error ;) (We should try to not let that happen) I tried to hand-craft my jmeter script the way I want externally using a tex editor, but this is what I got so far, and I haven't figured out why yet. The physical structure itself pass xml validation but seems it is a logical error. I was planning to do trial and error to pinpoint where the problem is, but Felix if you don't mind taking a quick look for me, I'll be very grateful. > Second, that that error is displayed and hidden behind the splash > screen. That should not be the case. Thanks for agreeing with that.
