ActiveState Community Site - Windows XP Pro - Comments

re: file associations

ToddW — Mon, 01 Dec 2008 21:10:33 +0000

I have not been able to reproduce any problems when setting the default file/edit associations (Windows XP Pro).

Are you using Komodo's "Windows Integration" preference and then clicking on the "Re-apply settings to System"?

If yes, are there any errors after trying to re-apply? You may also want to examine the Komodo log file to see if there are any exceptions (you will need to shutdown Komodo to ensure the log file is completely flushed/written out):
http://community.activestate.com/faq/komodo-file-locations#log_files

Cheers,
Todd

WriteRegistry Problems

devin — Mon, 01 Dec 2008 19:47:15 +0000

Hello Chris,

Not too much action on this topic. However, I am working with the MSI, and was intrigued by this problem. BTW, With a bit of experimentation, I did get it to work.

There are two issues: what is a file name that it is looking for, and the syntax is documented incorrectly for the values.

If you don't already have an MSI editor I would recommend getting Orca. It has helped me quite a bit. When I open up the MSI with Orca I found that there is a 'File' table in it. I used one of the file names from the table for ''. That got me past the file not found error.

The next problem is that 'Values' is defined as a array of hashes. When in fact the code is looking for an array of arrays. By modifying your code to look like this, I get an MSI file that has registry settings in it:

Values => [
['Serial', '1234'],
['Version', '2.0'],
],

BTW, I also found bug in the code where you can't create a Menu shortcut, and Desktop shortcut for the same thing.

Regards,

Devin

re: nice digging

ToddW — Mon, 01 Dec 2008 19:24:12 +0000

Hi AF,

That is certainly an unintentional side affect. Thanks for getting back to us about this problem and for providing the workaround.

I've added some notes to the Komodo bug about this particular problem.

Thanks,
Todd

Anybody?

corey1981 — Mon, 01 Dec 2008 14:49:03 +0000

Is no one else having this issue? No comment from the development team?

Problem and workaround found

alejandro_tomas_fritz — Mon, 01 Dec 2008 14:49:00 +0000

The problem that causes this is that the Komodo debugger is injecting a variable called DBGPHideChildren in the license module that causes mx validation of that module to fail.

This error is documented in:

http://www.nabble.com/DBGPHideChildren-variable-td20260988.html
http://bugs.activestate.com/show_bug.cgi?id=64497

The workaround suggested by Marc-Andre Lemburg from eGenix is:

# Before importing mxODBC for the first time, cleanup the license module:

import mx.ODBC.license
try:
    del mx.ODBC.license.DBGPHideChildren
except AttributeError:
    pass

# Now import mxODBC's subpackage:

import mx.ODBC.Windows

This works well on my environment (Komodo 4.4).

thanks to all that helped

rgds, af.

still in trouble

montklair — Sun, 30 Nov 2008 12:39:56 +0000

I have tried many thing in the past few months, still cant install File-BSDGlob on my system.
I am not sure if its gonna solve my problem of converting my script to exe, but right now I am just curious on how to install it knowing it doesnt exist in the ppm.
I tried MINGW, indigoperl, strawberry perl, Gnu make, dmake, nmake...everytime with an error message.
i will not post error messages for thing not related to activstate but any new advice suggestions are welcome.
anyone tried to install this file on an XP , with a ppm or manually or any other solution?
thanks.

here is a javascript macro

jolan — Fri, 28 Nov 2008 17:08:49 +0000

here is a javascript macro to open in browser
it's compatible with jstreedrive
it use mappped URIs

var uri=ko.views.manager.currentView.document.file.URI;

prefs = Components.classes["@activestate.com/koPrefService;1"].
			getService(Components.interfaces.koIPrefService).effectivePrefs;
var mapping = null;
if (prefs.hasPrefHere('mappedPaths'))
	mapping = prefs.getStringPref('mappedPaths');
if (!mapping) {
	return;
}

var paths = mapping.split('::');
var mappeduri = '', mappedpath = '';
for (var i = 0; i < paths.length; i++) {
	var data = paths[i].split('##');
	if (uri.indexOf(data[1]) == 0) {
		if (data[1].length > mappeduri.length) {
			mappeduri = data[1];
			mappedpath = data[0];
		}
	}
}

if (mappedpath) {
	var newpath = mappedpath + uri.slice(mappeduri.length);
	ko.browse.openUrlInDefaultBrowser(newpath);
}

Additional information from mx.ODBC

alejandro_tomas_fritz — Fri, 28 Nov 2008 15:08:08 +0000

I got some additional questions to ask suggested by the people behind mxODBC (http://www.egenix.com):

* Does the Komodo debugger change the way modules are imported or add
symbols to the module namespace after import ?

* Does the Komodo debugger change the Python import path or mechanism
in some way that could cause it to import a "license" module from somewhere else ?

It's also possible, though unlikely, that the debugger introduces
non-standard attributes in the license module at load-time which
cause the verification to fail - the license module content may
not change, since it is digitally signed.

Any help is welcome, af.

changed subject

alejandro_tomas_fritz — Fri, 28 Nov 2008 09:21:02 +0000

Changed subject and some part of my original post to focus better the thread as related to the debugger (which i understood now thanks to your answers).

af.

environment is the same

alejandro_tomas_fritz — Fri, 28 Nov 2008 09:07:06 +0000

Both environments are the same, only in "set" i got the PROMPT=$P$G wich does not appear in Edit|Preferences|Environment, but i can't imagine how this could affect.

thanks for hint, af.

It interessting, this

MagicMilamber — Fri, 28 Nov 2008 07:18:42 +0000

It interessting,

this morning I restarted Kommodo Edit and the Menus worked.
Yesterday I only did the automatic restart after installing the Update to

"Kommodo Edit, version 5.0.2, build 2604, platform win32-x86.
Built on Wed Nov 19 18:33:41 2008".

seem that not all is realy new initialized on this restart.

thanks so far

Ralf

PYTHONPATH or a xmODBC environment variable?

troyt — Thu, 27 Nov 2008 22:40:25 +0000

Are there any environment variables set in your regular shell which somehow point to to the xmODBC license? It might be worth doing a 'set' at the command line and comparing it to what's in Edit|Preferences|Environment

Possibly a corrupted download

troyt — Thu, 27 Nov 2008 22:27:58 +0000

It might be worth trying the download again via FTP:

ftp://downloads.activestate.com/Komodo/releases/5.0.2/Komodo-Edit-5.0.2-...

Let us know if that doesn't work.

still same error

alejandro_tomas_fritz — Thu, 27 Nov 2008 20:28:57 +0000

Thanks for the suggestions Todd, i tried both, checking "debug in separate console" and remote debugging and get the same error.

My colleagues working with same environment (Win XP, Activestate Python 2.4.3, Komodo 4.4, licensed mxODBC 3.0.2) get the same error.

best, af.

re: environment variables?

ToddW — Thu, 27 Nov 2008 20:00:39 +0000

I'm not really sure why it would run differently from the command line to the debugger.

A couple of things to try, to narrow this down would be:

When launching the Komodo debugger, check the "Debug in separate console"
Try remote debugging, i.e. starting the Python debugger from the command line:
C:\Program Files\ActiveState Komodo IDE 5\lib\support\dbgp\bin\pydbgp.py -d localhost:9000 yourscript.py
```
C:\Program Files\ActiveState Komodo IDE 5\lib\support\dbgp\bin\pydbgp.py -d localhost:9000 yourscript.py
```

Did those make any difference?

Thanks,
Todd