"Encountered an improper argument" hovering cursor over assignments and/or writelines

[louisd]

This has been plaguing me for eons.
It's kind of like the first time an optometrist corrects your vision and you realize you've been dealing with crappy vision up until that point... Well, I've had this issue with 2012MR1, and I just realized that on 2018R1 SP7 IT STILL PERSISTS. What the efffff Hexagon? How can you not fix this after over a dozen releases?

Here's the situation:
write routine.
add assignments
add file/writelines
hover over anything prior to executing, and it will give you the little box showing the resultant output for assignments or writelines.
execute the routine, and hover your cursor over ANY assign or writeline, even inadvertently, and you get this silly error pop up. "Encountered an improper argument" you have to click OK on to continue.
it makes doing any changes to assigns or writelines a fricken game. let's see how quickly you can move cursor to where you need it, click to place cusor then move mouse away from all other assigns or writelines, or else! bah! /endrant.

[AndersI]

I don't think I've ever seen that message in connection with assignments. Are you 100% sure that everything used in an expression has previously received a value? And that you have no division by zero in the variable's dependency chain?

[HxSwartwood]

I've heard having the edit window on a different monitor can do this. I'm not sure if this is what you are doing but i had to keep everything on one monitor due to the stupid "encountered an improper argument".

[louisd]

interesting, I do have edit window in a split screen... I'll try this out and get back to y'all.

[louisd]

ok so I put edit window back into PCDMIS main window frame (rather than it being detached/floating on separate screen), then stretched entire pcdmis main window across both screens. voila, no error anymore. I've been putting up with that crap for more years than I can recall, thanks HxSwartwood!

[HxSwartwood]

louisd Awesome! Glad i could help!

[louisd]

Problem solved! If you are seeing this error message, shove your edit window back into your main PCDMIS window frame, then stretch/resize the whole frame across both screens. Yet another compromise we have to make with the demon in order for it to work.

[Kp61dude!]

Problem solved! If you are seeing this error message, shove your edit window back into your main PCDMIS window frame, then stretch/resize the whole frame across both screens. Yet another compromise we have to make with the demon in order for it to work.

Don't celebrate for too long... you'll go back to splitting the screen soon due to annoyance. It'll be worth the pesky pop up error lol!

[louisd]

I created a case (#109278) to report the bug. I don't know any other ways to report bugs. Maybe in the next release, they can fix this crap.

[KIRBSTER269]

are you high?what makes you think this year will be any different from any other year?

[louisd]

lol, wishful thinking? maybe it was never reported?

[KIRBSTER269]

louisd Hexagon will take care of that bug for you

tenor.gif

[tking]

2018 R1 (something) and it does the same. My fix is save and quit, reload, continue. Repeat as necessary. Your description of attempting to continue is hilarious and described exactly what I was doing before. Not a fix but it soothes the demon for a bit, then hit with the same club when it gets cranky.

.02,

TK

[Martijn]

I had the same problem. I noticed it happend when I switched between different windows layout I made.
I kept one window layout and made a customized toolbar where I could switch between different
options I use, for example report window on/off or summary- command mode.
I never had that message after that.

[CodeWarrior]

Learn something new everyday, happens to me all the time