kX Editor oversight?

Russ · Feb 2, 2006, 05:10 AM

There are certain errors that the kX Editor does not check for (i.e. the necessary blank line after 'end'), and at least one of these errors could be a fairly big problem.

i.e.
'name'/'copyright'/'engine'/'created'/'comment'/'guid' can all be blank, or missing completely, and the kX Editor does not complain.

In the case of 'guid', this can be a bad thing. It is unlikely to happen, but it is possible, that while editing code for a plugin that is allready loaded, that you do something that comments out, or removes the 'guid' element from the code. If this were to happen and you commit the changes, the plugin disappears from the DSP window. Not only that, but the 'plugins' registry key disappears as well, so you cannot load any plugins. If you then reintialize the DSP, all you will see is some wires connected to phantom plugins, and if you then clear the DSP, and reintialize, all you get is a blank DSP window.

A reset global settings, followed by a reinitialize DSP, will fix it, but you will lose any plugins (and settings) that were not part of the kX install, and thus will have to re-register all of them.

To re-create (NOT RECOMMENDED):
Back-up the kX regisitry key.
Save your current configuration with all boxes checked (for easy restoration).
Open the DSP window and edit any loaded plugin (it does not have to be enabled or translated).
Comment out the 'guid' line or use a blank guid (empty quotes).
Commit changes (click on the green checkmark).

To fix (not all of the following steps may be necessary):
Restore global settings.
Reinitialize the DSP.
Quit kxmixer.
Restore your registry information from backup.
Restart kxmixer.
Load your saved config.

Again, this is an unlikley scenario (I only noticed it, because I did it intentionally to see what types of errors would get by the error checks), but possible.

thomasabarnes · Feb 2, 2006, 05:41 AM

Man, you are so dear here! Keep making your observations and posts, Russ!

Russ · Feb 2, 2006, 08:45 AM

I guess the issue is not only with KX Editor, but also with the plugin manager/loader/whatever. It would be good if kX Editor caught such errors, but the plugin manager/loader/whatever really should do some error checking of its own, and not accept microcode updates with bad code (I imagine the same thing would happen if we called update_microcode from C++, under similair conditions (that is probably what kX Editor is doing anyway)).

Russ · Aug 27, 2006, 08:44 AM

This issue appears to be better in 3538k. Although it still does not catch such errors, it seems to no longer wipe out the registry key.

Feb 2, 2006, 05:10 AM	#1
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,563 Rep Power: 62	kX Editor oversight? There are certain errors that the kX Editor does not check for (i.e. the necessary blank line after 'end'), and at least one of these errors could be a fairly big problem. i.e. 'name'/'copyright'/'engine'/'created'/'comment'/'guid' can all be blank, or missing completely, and the kX Editor does not complain. In the case of 'guid', this can be a bad thing. It is unlikely to happen, but it is possible, that while editing code for a plugin that is allready loaded, that you do something that comments out, or removes the 'guid' element from the code. If this were to happen and you commit the changes, the plugin disappears from the DSP window. Not only that, but the 'plugins' registry key disappears as well, so you cannot load any plugins. If you then reintialize the DSP, all you will see is some wires connected to phantom plugins, and if you then clear the DSP, and reintialize, all you get is a blank DSP window. A reset global settings, followed by a reinitialize DSP, will fix it, but you will lose any plugins (and settings) that were not part of the kX install, and thus will have to re-register all of them. To re-create (NOT RECOMMENDED): Back-up the kX regisitry key. Save your current configuration with all boxes checked (for easy restoration). Open the DSP window and edit any loaded plugin (it does not have to be enabled or translated). Comment out the 'guid' line or use a blank guid (empty quotes). Commit changes (click on the green checkmark). To fix (not all of the following steps may be necessary): Restore global settings. Reinitialize the DSP. Quit kxmixer. Restore your registry information from backup. Restart kxmixer. Load your saved config. Again, this is an unlikley scenario (I only noticed it, because I did it intentionally to see what types of errors would get by the error checks), but possible.

Feb 2, 2006, 05:41 AM	#2
thomasabarnes Long Time ***** Friend Join Date: Jan 2003 Location: USA Posts: 1,375 Rep Power: 0 System Specs	Man, you are so dear here! Keep making your observations and posts, Russ! __________________ May a song always touch you in a positive way. SONAR X1D Expanded, Windows 7 Pro 64Bit, MOTU UltraLite MK3, 150 GB HDD, 250 GB HDD, 1 TB x2 HDD 7200 rpm My Music Production: Top 40, Contemporary Christian, Pop/Rock, Decent Rap, Inspirationals, and Children Songs

Feb 2, 2006, 08:45 AM	Thread Starter #3
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,563 Rep Power: 62	I guess the issue is not only with KX Editor, but also with the plugin manager/loader/whatever. It would be good if kX Editor caught such errors, but the plugin manager/loader/whatever really should do some error checking of its own, and not accept microcode updates with bad code (I imagine the same thing would happen if we called update_microcode from C++, under similair conditions (that is probably what kX Editor is doing anyway)).

Aug 27, 2006, 08:44 AM	Thread Starter #4
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,563 Rep Power: 62	This issue appears to be better in 3538k. Although it still does not catch such errors, it seems to no longer wipe out the registry key.