Parameter editor: Encountered an improper argument.

Started by FWL, April 24, 2015, 09:34:41

Previous topic - Next topic

FWL

Hello everyone,

Recently I discovered that the parameter editor wont always open on my computer. A lot of times i'll get the message "encountered an improper argument". I was wondering if i am the only one and it has to do with my computer-setup or that there were changes in the parameter editor. I have Windows 7 64 bit and use Openmpt 32 bit.

Thanks in advance!

FWL

Saga Musix

That issue was supposed to be fixed several months ago, so please upgrade to the latest version.
» No support, bug reports, feature requests via private messages - they will not be answered. Use the forums and the issue tracker so that everyone can benefit from your post.

FWL

I have the latest version installed. version 1.24.04.00 32 bit

Saga Musix

Can you give a step-by-step description how you can reproduce the issue?
» No support, bug reports, feature requests via private messages - they will not be answered. Use the forums and the issue tracker so that everyone can benefit from your post.

FWL

Hello Saga,

Of course:

1. input some note and effect data
2. Ctrl-l to select column
3. Alt-b to open parameter editor
4. Parameter editor pops up
5. close parameter editor.
6. repeat steps 2 and 3.
7. error: improper argument

Saga Musix

I tried that and it worked as expected here. Just to go sure, does it happen for you if you just start OpenMPT, then create a new module, go to the pattern editor, press Ctrl+L, Alt+B, close editor and press Alt+B again?
» No support, bug reports, feature requests via private messages - they will not be answered. Use the forums and the issue tracker so that everyone can benefit from your post.

FWL

Yes, I've created a new module, entered some data and followed the previous mentioned steps. But it's somewhat erratic. Sometimes after a lot of tries, switching between Alt+B and the right click menu "visualize effect"  the parameter editor pops up again.

I've also tried with previous saved modules and it's the same.

Maybe i should try to reinstall Openmpt

FWL

Saga Musix

That's not going to change anything.
By any chance, do you use a non-standard DPI setting (i.e. not 96 DPI) in Windows?
» No support, bug reports, feature requests via private messages - they will not be answered. Use the forums and the issue tracker so that everyone can benefit from your post.

FWL

I don't think so. The setting in the screen configuration of windows 7 is 100% (standard). That would be 96 dpi isn't?

FWL

I did find out that there's a difference in the error occurence when i switch between power options High Perfomance and Automatic. When Automatic is chosen and the Aero theme is on, the error only seems to occur when i reopen the paramater on the same channel. 

Saga Musix

Sounds like there's a race condition somewhere then, but I still couldn't reproduce it. I might have to try it with Aero, I guess.
» No support, bug reports, feature requests via private messages - they will not be answered. Use the forums and the issue tracker so that everyone can benefit from your post.

FWL

So to be clear:

Aero: only when reopening on same channel
Classic theme: almost every time


Saga Musix

Can you check if this version works better for you? If not, I guess I'll require a memory dump to work with, as otherwise it would be pretty much guesswork what is going wrong here.
http://sagagames.de/stuff/mptrack.exe
» No support, bug reports, feature requests via private messages - they will not be answered. Use the forums and the issue tracker so that everyone can benefit from your post.

FWL

Hee Saga!

That did the trick! The downloaded version opens and reopens the parameter editor without a glitch in classic mode as wel as Aero.

Thank you very much for your speedy solution. What eventually was the cause of the problem?


Saga Musix

There were a couple of uninitialized variables used as divisors, and due to their nature of being uninitialized, they were sometimes 0, so that division went bang. I'm not quite sure how that ever worked.
» No support, bug reports, feature requests via private messages - they will not be answered. Use the forums and the issue tracker so that everyone can benefit from your post.