eXpresso 1.2.? Development Test 3

I have heard, but don't know for sure, that editing AutoHotkeySC.bin with Resource Hacker to replace the default icons with custom ones will work... Maybe try that?

Thanks for the release!

glad you did this Now I don't have to.

Sorry all for not getting this done, I had school work that took priority. gluxon, if you need help, let me know. I haven't done AHK in awhile, but I'll help if I can.

I miss the old name and icon. eXpresso sounds too much like a Java thing. And the tray icon looks a bit like Java, too.

Cool, I'll download this and work on integrating my changes this week sometime.

Sorry to rain on the parade, but I found a bug, and a nasty one at that.
Pressing the Enter key will cause some unexpected behavior; for example, try running any multilingual PA.c installer and use the keyboard to navigate it. Here's what happened to me:
* Run installer
* "Select language" screen comes up
* I press Enter, expect language to be English (default)
* eXpresso selects the next item in the language list (Catalan), then allows the enter keypress
* End result: Catalan installer

That's just one example; another is my programming IDE. There are a lot of value-entry fields in the IDE, and pressing Enter doesn't work (i.e. doesn't enter the value in the textbox; it's as if the keypress got "eaten" by a keyboard hook) when eXpresso's running.

(Strangely enough, Coffee didn't have that problem... not trying to poke at eXpresso, just wondering a bit)

Thanks for taking this over. How to transfer associations from CAFE MOD to eXpresso? Or do you need to start from scratch there?

When double clicking a new extension, Expresso still C.A.F.E. (Accented 'E').

I'm really gonna try to get my mouse hook in there tomorrow for some limited (private?) beta testing. Just haven't had time yet

I currently use PFA for similar functionality.

Can someone explain the differences between the apps?

(NOTE: I have downloaded eXpresso to take look at it, but currently have PFA auto-starting. Obviously, I'd choose one or the other in the long run, and preferably one would be integrated directly into the platform.)

There's a bug when you cancel adding an association: the tooltip pops up and says "eXpresso successfully added a new association" or something like that. Here's the patch; it's in eXpresso.ahk, near the end of the code.

If opener
{
opener:=GetRelPath(A_ScriptFullPath,opener)
IniWrite, %opener%, %inifile%, %section%, %extension%
opener:=GetAbsMovPath(opener)
Run, "%opener%" "%filename%",,UseErrorLevel
}

#Persistent
TrayTip, eXpresso:, A new association has sucessfully been added.
SetTimer, RemoveTrayTip, 10000
return


needs to be changed to

If opener
{
opener:=GetRelPath(A_ScriptFullPath,opener)
IniWrite, %opener%, %inifile%, %section%, %extension%
opener:=GetAbsMovPath(opener)
Run, "%opener%" "%filename%",,UseErrorLevel

#Persistent
TrayTip, eXpresso:, A new association has sucessfully been added.
SetTimer, RemoveTrayTip, 10000
return
}

One other bug I noticed: eXpresso really slows down Enter handling. Without eXpresso running, pressing Enter is handled almost instantaneously; with eXpresso running, there's a half-second lag or so between the time I press Enter and the time it's handled. (This happens in Notepad, in Firefox, in Notepad++, in OOo, and in every other app I use)

Ok, this will probably firmly establish my computer as broken to you guys... but that's a risk I'm going to run.

First, double-clicking something that isn't a file treats it like a file anyway. For example, open Firefox, go into about:config, and double-click any setting; instead of the pref-editing box coming up, eXpresso traps the double-click and asks if you want to create a file association for the "file".

Next, the "Do you want to add a file association" box frequently freezes - clicking "Yes", "No", or "Cancel" has exactly no effect. Worse still, the dialog appears to be eating all mouse clicks...

I'm getting near to finishing my changes. So far so good. I'm still trying to work out one little thing (might just let it go...).

Re: SysListView32... noooooo those are all list views, and that's a control class, not a window class. There's no good way to prevent the thing with the Open File dialog: 1) it has a generic dialog window class (I suppose we could build in a better black list, right now it just blacklists 'Control Panel'), 2) the window title of the Open File dialog can be customized, so it might change.

Oh, and another thing you'll have to handle in your launcher:

When choosing the Refresh eXpresso menu option or removing a managed window class (which triggers the same refresh), the app is relaunched. This tricks your launcher into thinking eXpresso has exited and removes the INI file, oops. My suggestion to work around it would be to have your launcher's RunWait() sit in a loop. Once eXpresso closes, wait like 2 or 3 seconds and see if it comes back (the reload should be near instant). You can use my ProcFunc header here:

https://portableapps.com/node/12561

and use ${ProcessExists} and ${ProcessWaitClose} function to wait for the new instance to close. If no new instance appears within 2 seconds or so, then you can safely cleanup and exit.

It might be an idea to try replacing tray tips with toaster popups, as they are more flexible.
Great work so far guys, can't wait to see wraithdu's fixes.
Regarding the enter lag, you could replace the enter code with #IfWinActive, but this wouldn't work for alternative file managers.
Also, double-clicking on an explorer window to maximise it reloads eXpresso.
EDIT: Why not add in a command line switch to tell it where expresso.ini is? it would avoid having to move the file and fix the problem with the launcher moving it prematurely.

I'm definitely stuck on this other little thing...if you double click an already selected file on the file name, not the icon, it will trigger the slow-double-click-rename function. This happens when a selected file is clicked on the name outside of the double click time. There doesn't seem to be a time limit here either, I've tried waiting a few minutes between clicks and it still renames the file. The original CAFE had this problem also, and happens because the second click of a double click is eaten by cafe, leading to a single click on a (possibly) already selected file. I can't think of a good solution quite yet.

I wonder if there's an API call to disable this feature? Then we could temporarily disable it then re-enable it.

For some reason, my file associations are not remembered when I switch PC's.

I'm gonna try a reinstall when I get home, but I don't think it'll work, considering this is a new flashdrive.

Restarting eXpresso (either via right-click and hitting "Refresh eXpresso" or just relaunching it) causes it to lose all its settings, including associations. Closing it down completely and starting again brings them all back, but still a pretty nasty bug nonetheless. It actually scared me at first, because I have quite a few associations that I don't feel like redoing all over again.

As best as I can see reading source in plain old notepad (ha!) you're still going to have problems here:

FindProcDLL::FindProc "${APPNAME}.exe"

because the launcher is going to find itself and you'll allways get TRUE out of this test.

Additionally you are relaunching the launcher from within eXpresso with the '-restart' switch. The other problem with this is now you have THREE instances of eXpresso.exe in existence (original launcher, actual eXpresso app, and the new launcher) and there's no way the new launcher instance will work right. Even assuming you change the launcher name to something different, you still have introduced a race condition... will the new launcher get to the FindProc code before the old instance of eXpresso ends??? There's no way to know for sure, and if it does, then your relaunch fails. I really think the loop that I had is your best option, and you'll have to rename the launcher to support the 'Reload' command.

Your only other option is to change eXpresso to read the INI from the Data\Settings directory so it is never moved. Then you can run eXpresso via Exec (instead of ExecWait) from the launcher and not have to worry about reloads at all.

Well, looks like the double-click "fixes" actually made everything worse. It seems that while eXpresso is active now, double-clicks on many things don't register. It took me a bit to realize this; I actually thought the mouse I was using at the time was going bad, until I went onto my netbook and had the same problem, then I realized eXpresso was the culprit.

Even more strangely, the problem gets even worse if eXpresso is paused. In that case, double-clicks stop working entirely.

This issue makes eXpresso completely unusable. Please fix ASAP! (Or at least give me a link to Dev Test 2 in the meantime...)