Calling All Programmers!!!

[Doomulation]

Faaast fast post just to give you the crappy news - the right-click context menus *still* come up with the 'multiple instances' error. Urgh :S

Ahahah... I was investigating something and had "put back" that bug to investigate it. I forgot to change it back again. But this time I've truly fixed it!!

'Doom's Infested Key' also crashed on me for the first time when I tried adding a keyword to a website manually through the menu. It worked most of the time, but crashed that once :S

Yeah, well, it doesn't want to crash. Unless you can re-create it and tell me how to do it, then there's no way to fix it.

(To get my keyword box error repitition, like you asked... type in a bad keyword, something wrong. An error pop-up will appear. Press F12 to close the keyword box. Press F12 to open it again... the same error will still be displayed. It doesn't seem to fade away or go away, at least not on the machine I'm using at the minute...)

Fixed

[EDIT: IMPORTANT ERROR!!! Currently you can select folders in the Command Management window and assign them keywords, but these keywords do NOT work - it says it can't find the file specified. Could this be fixed in the next release along with the other bug fixes and tweaks?]

Also fixed

A little progress update as well...

- Hotkey support will be in next version!!
- Keyword box is now always on top!
- Commands are sorted alphabertically ascending!
- Sounds are now optional.
- Changed directinput to action mapping - much more powerful and easier for me (the only drawback is that you will not be able to use modifier keys (eg, alt, shift, etc) AND another key for an effect, but still, now you can also use gamepads and stuff =))
- Logging: now every error it encounters are logged to Errors.log. Just zip it up and post it if you encounter errors.
- Also helped a little when the Shell API seems busy at times. The app will prompt you this.
- There's probably more, but that's all I can remember.

New version is coming tonight (hopefully)!
So you know, my timezone is GMT + 1

EDIT: Okay, here we go again. Beta 2. This should contain the last of the functions that should make it into release 1.0. Now it's just TEST, TEST, TEST, TEST! You could give it out to the others too so they may test this before an official release.

How are the icons and documentation coming btw?

 

[Xade]

Hooray! It's sounding incredible.

Yeah, I'm on standard GMT myself. I won't bother posting the to-do list here right now; if you're looking for stuff to change in the program you can check back to that last one I posted yesterday.

Obviously there'll be another full report after this new beta you're posting

Can't wait...

 

[Doomulation]

In case you missed it, which I do think you did, the new beta is already available.
Edited 19:43, while you posted 19:41. Meh!

 

[DeathRain99]

Mmm, it didn't appear to run...

Error Log:

pOptionsDlg->ShowWindow(SW_MINIMIZE) FAILED in [Init].
pManageDlg->ShowWindow(SW_MINIMIZE) FAILED in [Startup].
pGraph->RenderFile FAILED in PlayVoice with HRESULT: 0x80040200 (DIERR_INSUFFICIENTPRIVS & VFW_E_INVALIDMEDIATYPE)
pGraph->FindFilterByName FAILED in PlayVoice with HRESULT: 0x80040216 (VFW_E_NOT_FOUND)
PlayVoice: Was trying to play file [Sounds\Greedy.mp4].
PlayVoice FAILED in [Check For Other Instances] with HRESULT: 0x80040216 (VFW_E_NOT_FOUND)


(...mmm....autoit....)

 

[Xade]

Whoah... impressive.

That's easily the most solid release yet, and I like it. A lot.

There's very little left to do before we move on to the text modifcation/icons/header names now, to be honest.

Although, that said, here's the latest report...

Potential Fixes:

- Folders can't be right-clicked yet and keyworded. I personally think that this should be the last *big* feature to make the cut for v1.0; I reckon it's quite an important feature that should probably be in there. Whether it *can* be done, of course, might be another matter.
- Hotkey selection presents a screen allowing you to select a 'Player'; presumably this screen is part of a game control interface. Could it be neatened or could this be modified?
- IMPORTANT! Keywords added through the right-click menu appear in the list that's presented to you when you add them, and appear there in future when you right-click and keyword other files... BUT they don't appear in the main 'Manage Commands' window in future. Right-clicked keywords don't get added to the main list of commands, just the right-click keyword manager. As a result, there is no way to modify/delete them later, as they don't appear in the normal command manager.
- If you choose to 'Overwrite an existing keyword', the keyword in question doesn't get over-ridden. Another keyword of the same name is just added to the list instead of the old one being removed/deleted. This issue should probably be resolved.
- Can't delete keywords by pressing 'delete'; can't view file paths. Obviously this is due to you not implementing the 'edit' feature yet, but... perhaps this should also make it for the v1.0 release?
- Go to 'Manage Commands' and click the 'Browse' button. It says 'Folder:' in the bottom left. Perhaps this should be changed to 'Item:' or 'Path:'?
- 'Options' and 'Manage Commands' windows both don't default to being 'always on top' the same way the keyword box does. Could they also be made to be always on top?
- Error messages (such as the 'multiple instances' error, for example) don't appear on top of other windows; often pop up underneath them. Could something be done about that?
- First time I ran this version, the keyword box, when called up, appeared in the top left instead of the middle. When I dragged it to the middle, it appeared there in future. Just a glitch or a minor bug?

Potential Tweaks:

- A 'Clear All Keywords' command or function; perhaps in the 'Options' menu. Basically a Quicklinks 'Reset' button or command that would get rid of all registry entries previously made; keywords etc, allowing the user to clean up all registry entries Quicklinks had made. Perhaps an option dialogue would be presented - "Reset all keywords and settings? 'Yes', 'Cancel'.
- Defaulting sounds to 'Off' on first program load? Then they could be enabled later if the user wished.

Potential To-Do List:

- Bug fixes and tweak implentations above.
- Possible integration of hotkey modifying into the Quicklinks GUI as before?
- An 'About' box explaining program coder and "inventor"/collaborator, copyright of code and concept, etc.
- Right-click folder 'Keyword It!' context menu option that works just the same as it does for files. (I think this should make v1.0. Yeah, IE intergration etc can wait until a later release, along with smart keyword searching and that stuff.)
- Modification of text, icons and window headers. (I'll supply you with a .txt of these possible changes, and hopefully a couple of .ico files for the icons).
- Readme (Again, I'll take care of this).
- ...Loads more testing and a big report on the next beta release?!

This version of Quicklinks is easily the best yet, save for the problem with the right-click keywording not registering with the main command manager list.

I'm using Quicklinks stacks now just as part of using the PC. It fades into the background easily and just becomes a part of Windows - exactly what it should do. It's simple, useful, and does exactly what it was intended to do.

To be honest, right now I guess the focus should be on everything mentioned above. Any features not involved there (smart keywording, IE integration, scripts...) should probably be left alone until we have an absolutely flawless v1.0 up and running with all the basic functions.

I think we are probably only a couple of betas away from a total v1.0 release. If you iron out *everything* listed above, all that'll be left to do will be the branding side of things (re-texting, icons etc...) and the readme. After that... we're looking at Quicklinks 1.0! Public release beckons, eh...?

Solid work, Doom. Loving it. Roll on beta 3, damned it!

[EDIT: Oh crud, check the guy's error log above.]

[EDIT 2: ...Perhaps, for the time being (v1.0?) sounds might need to get left alone/removed until a post-1.0 version? They seem to be causing some troubles.

 

[smcd]

*whistles and grins mischievously* my crappy program is pretty solid (and getting rewritten to use mainly menus and 3 separate configuration dialogs for files, folders, and websites). Sometimes too much glitter and not enough glue makes for a mess Anyhow, I can't get your code to compile doom, it gripes about unresolved externals in the linking process... probably because I don't have the DirectX sdk installed. After I get some sleep I'll grab the latest wip and help test though I suppose.

 

[Doomulation]

DeathRain99:
Sorry, that log doesn't tell me much. It tells me that your computer can't play aac files - but aside from that...
Are you just trying to run the program? Did it crash, or did you get an error message? I might improve the logging in a next version if I get enough information.

Whoah... impressive.

That's easily the most solid release yet, and I like it. A lot.

There's very little left to do before we move on to the text modifcation/icons/header names now, to be honest.

Although, that said, here's the latest report...

Potential Fixes:

- Folders can't be right-clicked yet and keyworded. I personally think that this should be the last *big* feature to make the cut for v1.0; I reckon it's quite an important feature that should probably be in there. Whether it *can* be done, of course, might be another matter.

I suppose I could try... the shell integration and launch isn't perfect yet; it isn't flawless.

- Hotkey selection presents a screen allowing you to select a 'Player'; presumably this screen is part of a game control interface. Could it be neatened or could this be modified?

Yes, it's actually a game control interface created by DirectInput. IT could be modified via a very advanced, complex way, but it's not my source, so there is not much I can do about it other than that.

- IMPORTANT! Keywords added through the right-click menu appear in the list that's presented to you when you add them, and appear there in future when you right-click and keyword other files... BUT they don't appear in the main 'Manage Commands' window in future. Right-clicked keywords don't get added to the main list of commands, just the right-click keyword manager. As a result, there is no way to modify/delete them later, as they don't appear in the normal command manager.

I'll look into that.

- If you choose to 'Overwrite an existing keyword', the keyword in question doesn't get over-ridden. Another keyword of the same name is just added to the list instead of the old one being removed/deleted. This issue should probably be resolved.

Heh. Yes, it will be fixed.

- Can't delete keywords by pressing 'delete'; can't view file paths. Obviously this is due to you not implementing the 'edit' feature yet, but... perhaps this should also make it for the v1.0 release?

Easy enough I guess. I will look into both those things.

- Go to 'Manage Commands' and click the 'Browse' button. It says 'Folder:' in the bottom left. Perhaps this should be changed to 'Item:' or 'Path:'?

I can try. This isn't my dialog; it's a dialog built into Windows Shell shown as a result of me calling an API.

- 'Options' and 'Manage Commands' windows both don't default to being 'always on top' the same way the keyword box does. Could they also be made to be always on top?

Of course.

- Error messages (such as the 'multiple instances' error, for example) don't appear on top of other windows; often pop up underneath them. Could something be done about that?

I honestly don't know. Might work if I use some extra flags.

- First time I ran this version, the keyword box, when called up, appeared in the top left instead of the middle. When I dragged it to the middle, it appeared there in future. Just a glitch or a minor bug?

I would say - a glitch.

Potential Tweaks:

- A 'Clear All Keywords' command or function; perhaps in the 'Options' menu. Basically a Quicklinks 'Reset' button or command that would get rid of all registry entries previously made; keywords etc, allowing the user to clean up all registry entries Quicklinks had made. Perhaps an option dialogue would be presented - "Reset all keywords and settings? 'Yes', 'Cancel'.

As good as done.

- Defaulting sounds to 'Off' on first program load? Then they could be enabled later if the user wished.

Then the user wouldn't hear the first run sound. That is basically the one sound that will make the user decide if he or she wants to keep them or not.

Potential To-Do List:

- Bug fixes and tweak implentations above.
- Possible integration of hotkey modifying into the Quicklinks GUI as before?
- An 'About' box explaining program coder and "inventor"/collaborator, copyright of code and concept, etc.
- Right-click folder 'Keyword It!' context menu option that works just the same as it does for files. (I think this should make v1.0. Yeah, IE intergration etc can wait until a later release, along with smart keyword searching and that stuff.)
- Modification of text, icons and window headers. (I'll supply you with a .txt of these possible changes, and hopefully a couple of .ico files for the icons).
- Readme (Again, I'll take care of this).
- ...Loads more testing and a big report on the next beta release?!

This version of Quicklinks is easily the best yet, save for the problem with the right-click keywording not registering with the main command manager list.

I'm using Quicklinks stacks now just as part of using the PC. It fades into the background easily and just becomes a part of Windows - exactly what it should do. It's simple, useful, and does exactly what it was intended to do.

To be honest, right now I guess the focus should be on everything mentioned above. Any features not involved there (smart keywording, IE integration, scripts...) should probably be left alone until we have an absolutely flawless v1.0 up and running with all the basic functions.

I think we are probably only a couple of betas away from a total v1.0 release. If you iron out *everything* listed above, all that'll be left to do will be the branding side of things (re-texting, icons etc...) and the readme. After that... we're looking at Quicklinks 1.0! Public release beckons, eh...?

Solid work, Doom. Loving it. Roll on beta 3, damned it!

[EDIT: Oh crud, check the guy's error log above.]

[EDIT 2: ...Perhaps, for the time being (v1.0?) sounds might need to get left alone/removed until a post-1.0 version? They seem to be causing some troubles.

For edit 2, betas will continue to be released until it appear solid enough for a release - after all, that's what they are for.

Seth:
It might be because of that, yes... Perhaps if you told me what symbols, I could help. The latest wip links against yet another library, so hehe...


EDIT: Beta 3.
Changes:

- Folders can now be right-clicked.
- Old command now disappear (or is replaced) by the new one if you choose to overwrite.
- Options and Manage Commands dialogs are now always on top.
- A reset all settings feature was added.
- About box was finally finished and added to tray menu.

What was not added / could not be added:

- Hotkey selection presents a screen allowing you to select a 'Player'; presumably this screen is part of a game control interface - this could not be added; I have no control over that screen.

- Keywords added through the right-click menu appear in the list that's presented to you when you add them, and appear there in future when you right-click and keyword other files... BUT they don't appear in the main 'Manage Commands' window in future. Right-clicked keywords don't get added to the main list of commands, just the right-click keyword manager. As a result, there is no way to modify/delete them later, as they don't appear in the normal command manager - I could not find this bug.

- Can't delete keywords by pressing 'delete'; can't view file paths. Obviously this is due to you not implementing the 'edit' feature yet, but... perhaps this should also make it for the v1.0 release? - could not find this bug

- Go to 'Manage Commands' and click the 'Browse' button. It says 'Folder:' in the bottom left. Perhaps this should be changed to 'Item:' or 'Path:'? - Again, this is not possible (or maybe it is... through a... dare I say it?--a HACK!

- Error messages (such as the 'multiple instances' error, for example) don't appear on top of other windows; often pop up underneath them. Could something be done about that? - I don't know about this. I don't know why they disappear. Perhaps it is because some of them belongs to no window. I don't know if this fixes it, but I changed it a little.

- First time I ran this version, the keyword box, when called up, appeared in the top left instead of the middle. When I dragged it to the middle, it appeared there in future. Just a glitch or a minor bug? - A glitch presumably, because I have not encountered this.

- Defaulting sounds to 'Off' on first program load? Then they could be enabled later if the user wished. - As stated above, it will default to on.

- Possible integration of hotkey modifying into the Quicklinks GUI as before? -
Too much work; and too time consuming - maybe next release, but only MAYBE

 

[DeathRain99]

It didn't really do anything to tell you the truth. I just ran it, and it didn't open or anything, and that's what what is my error log.

Since I can't really see what the program is like, it' shard to recommend something, but perhaps you could make like something that they could create their own tabs in a dropdown combobox type of thing...

If you're using Autoit (I can't tell), it could be something like:

#include <GUIConstants.au3>
$Form1 = GUICreate("Select Emulator", 240, 150, 0, 0)
$Button1 = GUICtrlCreateButton("Run Emulator", 75, 80, 75, 25)
$Combo1 = GUICtrlCreateCombo("", 32, 24, 145, 21)
GUICtrlSetData(-1, "Project64|Project64K|ePSXe|SNES9X|VisualBoyAdvance|MAME","Project64")
GUISetState(@SW_SHOW)


While 1
$msg = GuiGetMsg()
Select
Case $msg = $GUI_EVENT_CLOSE
ExitLoop
Case $msg = $Button1
$emu = GUICtrlRead($Combo1)
if $emu = "Project64" then Run("C:\Emulation\Emulators\Project64 1.6\Project64.exe")
if $emu = "Project64K" then Run("C:\Emulation\Emulators\Project64k_0_13\Project64k.exe")
if $emu = "ePSXe" then Run("C:\Emulation\Emulators\EPSXE 1.6\ePSXe.exe")
if $emu = "SNES9X" then Run("C:\Emulation\Emulators\snes9x\snes9xw.exe")
if $emu = "VisualBoyAdvance" then Run("C:\Emulation\Emulators\VisualBoyAdvance-1.8.0-beta2\VisualBoyAdvance.exe")
if $emu = "MAME" then Run("C:\Emulation\Emulators\mame32k0.64en\mame32k.exe")
; if ... keep going ...
;
EndSelect
WEnd
Exit

However, I'm kinda a noob so I don't know how to let the user create it's personal dropdown without editing the script.

(Sorry if this is a waste, or if you're not even using Autoit, the form of the error log looked a bit like it though)

^^The script above is what I use for myself, as it's paths are customized...anyways...

 

[Doomulation]

It's all custom made. I can't do anything unless I get more information. The application resides in the system tray. According to the log, everything is going fine: no problems.

 

[DeathRain99]

Yeah, but I've checked in my tray, and it doesn't appear that it isrunning... Just my router, volume, and azureus.

--Will edit after I try latest beta

Edit: Well that was quick enough. Beta 3 worked for me. I like how the program called me master, keep that in there for sure.

 

[Xade]

Hey-hey,

Alright; weirdness. I tried this on yet another machine and, bizarrely, just like Death said, it didn't load. No errors, no screens... nothing. I'll post the error log soon.

However, I tried it on the machine I usually use with it, and... well, after telling me it couldn't register my commands, it loaded successfully.

Bizarre.

That aside, the report, as ever...

Potential Fixes:

- ISSUE: The 'Manage Commands' list is ONLY updated with the commands added through 'Keyword It!' every time Quicklinks is restarted. If you right-click a file and keyword it, you need to close the program and then re-open it for that keyword to appear in the main 'Manage Commands' window. Hopefully there might be a simple solution to that along the lines of having the 'Manage Commands' window refresh its list every time it's called down? Or something?!
- Probably related to the problem above, if you clear all settings using the Options dialogue, keywords don't disappear from the main 'Manage Commands' window; you need to restart the program for the list to clear itself.
- Error: There is an issue regarding 'terminating threads' and keywords assigned to deleted/moved files. If you create an error by keywording a deleted file, the error message won't disappear. If you try to close the keyword box by hitting F12, an error is presenting about trying to execute the current command. If you select 'Yes' to terminate this execution, you are presented with an error saying 'Unable to terminate command - you'll have to wait'. Is this fixable so that errors don't jam the program/keyword box? From whenever you create this error by deleting a keyworded file, you CANNOT use any other program functions without being asked to terminate the command, which doesn't work. Even if you do terminate the command, the same error will keep coming back after you press every hotkey.
- Still can't press the delete key on commands in the 'Manage Commands' window to delete them. But, like you said, when you allow keyword editing in the list, hopefully this will also be allowed.
- Possible stability issues associated with error handling. Again, these may be revealed in error logs.
- Sounds don't seem to function. If you really think sounds are required, perhaps a more universal sound format such as .WAV/.mp3 would be appropriate?
- Already mentioned, but if you try to run another instance of Quicklinks/it can't register your commands on first load, the error box you're presented with appears UNDER the folder that Quicklinks is in. May be tough to fix?
- Mysterious non-starts on a number of systems. No errors presented, just a non-loading of the program. Keylog to follow.

Potential Tweaks:

- Changing the 'tick' boxes from the bottom two Options menu commands to proper dialogue buttons?
- The aforementioned hotkey integration into the GUI, though, as you say, this might well be a bitch of a job and take a long time.
- An editable keyword list in the 'Manage Commands' window that displays the keywords and what they're assigned to in the two text boxes below the list, and allows deletion.

Potential To-Do List:

- Bug fixes and tweak implentations above.
[Copied from earlier:]
- Modification of text, icons and window headers. (I'll supply you with a .txt of these possible changes, and hopefully a couple of .ico files for the icons).
- Readme (Again, I'll take care of this).
- A shit-load of testing on the next beta, and *especially* trying Quicklinks on several different PCs by several different people. It seems to have an effect...

 

[Doomulation]

- ISSUE: The 'Manage Commands' list is ONLY updated with the commands added through 'Keyword It!' every time Quicklinks is restarted. If you right-click a file and keyword it, you need to close the program and then re-open it for that keyword to appear in the main 'Manage Commands' window. Hopefully there might be a simple solution to that along the lines of having the 'Manage Commands' window refresh its list every time it's called down? Or something?!
- Probably related to the problem above, if you clear all settings using the Options dialogue, keywords don't disappear from the main 'Manage Commands' window; you need to restart the program for the list to clear itself.

Yes, yes, both should be solved by updating the list each time it's shown. I'll change it so.

- Error: There is an issue regarding 'terminating threads' and keywords assigned to deleted/moved files. If you create an error by keywording a deleted file, the error message won't disappear. If you try to close the keyword box by hitting F12, an error is presenting about trying to execute the current command. If you select 'Yes' to terminate this execution, you are presented with an error saying 'Unable to terminate command - you'll have to wait'. Is this fixable so that errors don't jam the program/keyword box? From whenever you create this error by deleting a keyworded file, you CANNOT use any other program functions without being asked to terminate the command, which doesn't work. Even if you do terminate the command, the same error will keep coming back after you press every hotkey.

This "error" happens when the ShellExecute API is busy. Therefore I run it in its own thread, so I can detect when it happens. The application asks you if you want to terminate that thread if that happens, and prompt you an error if you fail. The thing is that if this "error" freezes the dialogs, and that wouldn't be very nice, would it?

- Still can't press the delete key on commands in the 'Manage Commands' window to delete them. But, like you said, when you allow keyword editing in the list, hopefully this will also be allowed.

The delete key on the keyboard, like a shortcut?

- Possible stability issues associated with error handling. Again, these may be revealed in error logs.

Perhaps. But I need to know what errors.

- Sounds don't seem to function. If you really think sounds are required, perhaps a more universal sound format such as .WAV/.mp3 would be appropriate?

They don't? Hmm... What seems to happen?
And why do I not use WAV/MP3? Wav is way too big; mp3 can't be compressed enough plus I wish to promote aac, because it's pretty much THE best format out there right now.

- Already mentioned, but if you try to run another instance of Quicklinks/it can't register your commands on first load, the error box you're presented with appears UNDER the folder that Quicklinks is in. May be tough to fix?

^^" Okay, I'll change it; but hopefully I will be able to put the shell code in its own Dll, which will result in the removal of these errors.

- Mysterious non-starts on a number of systems. No errors presented, just a non-loading of the program. Keylog to follow.

Hmmm. Well, currently the log only contains errors. I may have to log events, too, to solve this problem. To see what the heck is going on.

Potential Tweaks:

- Changing the 'tick' boxes from the bottom two Options menu commands to proper dialogue buttons?

I don't know. Make a poll; see what they like most.

- The aforementioned hotkey integration into the GUI, though, as you say, this might well be a bitch of a job and take a long time.

This is more a pain in the ass than you understand. First, the current implemtation will not support this. I use action mapping, which pretty much means that the API will return if wether the user has pressed the right key for an "action." It doesn't matter if it's F1, F2 or whatever, it still returns if action "X" has been pressed. Plus, I need to TRANSLATE all the keys that are pressed to text; store this configuration somehow, and so on. Too much work.

- An editable keyword list in the 'Manage Commands' window that displays the keywords and what they're assigned to in the two text boxes below the list, and allows deletion.

Alright, the next release for that.

 

[Xade]

Hey-hey, sorry...

Brief update - another error...

- Keywords can now be assigned to the Recycle Bin, My Computer, Internet Explorer etc... but when the window opens, the 'Executable:' section is empty; there is no path provided for you to assign the keyword to.

[EDIT: Another!

- Right-clicking the E: drive when a CD is inserted and selecting 'Keyword It!' currently causes an error in Doom's Infested Key; an error dialogue is presented.]

Oh, and the log. This may be from more than one version mind; the last two betas, possibly:

pOptionsDlg->ShowWindow(SW_MINIMIZE) FAILED in [Init].
pManageDlg->ShowWindow(SW_MINIMIZE) FAILED in [Startup].
pOptionsDlg->ShowWindow(SW_MINIMIZE) FAILED in [Init].
pManageDlg->ShowWindow(SW_MINIMIZE) FAILED in [Startup].
pManageDlg->ShowWindow(SW_SHOW) FAILED in [Register Command].
pOptionsDlg->ShowWindow(SW_MINIMIZE) FAILED in [Init].
pManageDlg->ShowWindow(SW_MINIMIZE) FAILED in [Startup].
pManageDlg->ShowWindow(SW_SHOW) FAILED in [Register Command].
pOptionsDlg->ShowWindow(SW_MINIMIZE) FAILED in [Init].
pManageDlg->ShowWindow(SW_MINIMIZE) FAILED in [Startup].
pManageDlg->ShowWindow(SW_SHOW) FAILED in [Register Command].
pOptionsDlg->ShowWindow(SW_MINIMIZE) FAILED in [Init].
ACCESS VIOLATION in CManageCommandsDlg::OnInitDialog [Registry.EnumValues]
ACCESS VIOLATION in CManageCommandsDlg::OnInitDialog [Registry.EnumValues]
ACCESS VIOLATION in CManageCommandsDlg::OnInitDialog [Registry.EnumValues]
pManageDlg->ShowWindow(SW_MINIMIZE) FAILED in [Startup].
dlg.ShowWindow(SW_HIDE) FAILED in [Init].
Registry.DeleteValue FAILED in CManageCommandsDlg::OnBnClickedButtonRemove with HRESULT: 0x2 (ERROR_FILE_NOT_FOUND)
Registry.DeleteValue FAILED in CManageCommandsDlg::OnBnClickedButtonRemove with HRESULT: 0x2 (ERROR_FILE_NOT_FOUND)
Registry.DeleteValue FAILED in CManageCommandsDlg::OnBnClickedButtonRemove with HRESULT: 0x2 (ERROR_FILE_NOT_FOUND)
Registry.DeleteValue FAILED in CManageCommandsDlg::OnBnClickedButtonRemove with HRESULT: 0x2 (ERROR_FILE_NOT_FOUND)
Registry.DeleteValue FAILED in CManageCommandsDlg::OnBnClickedButtonRemove with HRESULT: 0x2 (ERROR_FILE_NOT_FOUND)
Registry.DeleteValue FAILED in CManageCommandsDlg::OnBnClickedButtonRemove with HRESULT: 0x2 (ERROR_FILE_NOT_FOUND)
Registry.DeleteValue FAILED in CManageCommandsDlg::OnBnClickedButtonRemove with HRESULT: 0x2 (ERROR_FILE_NOT_FOUND)
Registry.DeleteValue FAILED in CManageCommandsDlg::OnBnClickedButtonRemove with HRESULT: 0x2 (ERROR_FILE_NOT_FOUND)
pGraph->RenderFile FAILED in PlayVoice with HRESULT: 0x80040216 (VFW_E_NOT_FOUND)
pGraph->FindFilterByName FAILED in PlayVoice with HRESULT: 0x80040216 (VFW_E_NOT_FOUND)
PlayVoice: Was trying to play file [Sounds\Exit.mp4].
PlayVoice FAILED in [Post-Init] with HRESULT: 0x80040216 (VFW_E_NOT_FOUND)
pOptionsDlg->ShowWindow(SW_MINIMIZE) FAILED in [Terminating].
pManageDlg->ShowWindow(SW_MINIMIZE) FAILED in [Terminating].
pOptionsDlg->ShowWindow(SW_MINIMIZE) FAILED in [Init].
pManageDlg->ShowWindow(SW_MINIMIZE) FAILED in [Startup].
pManageDlg->ShowWindow(SW_SHOW) FAILED in [Register Command].
pOptionsDlg->ShowWindow(SW_MINIMIZE) FAILED in [Init].
pManageDlg->ShowWindow(SW_MINIMIZE) FAILED in [Startup].
pManageDlg->ShowWindow(SW_SHOW) FAILED in [Register Command].
pOptionsDlg->ShowWindow(SW_MINIMIZE) FAILED in [Init].
pManageDlg->ShowWindow(SW_MINIMIZE) FAILED in [Startup].
dlg.ShowWindow(SW_HIDE) FAILED in [Init].
PlayVoice FAILED in [First Run].0x2 (ERROR_FILE_NOT_FOUND)
pOptionsDlg->ShowWindow(SW_MINIMIZE) FAILED in [Terminating].
pManageDlg->ShowWindow(SW_MINIMIZE) FAILED in [Terminating].
dlg.DestroyWindow FAILED in [Terminating].
pOptionsDlg->ShowWindow(SW_MINIMIZE) FAILED in [Init].
pManageDlg->ShowWindow(SW_MINIMIZE) FAILED in [Startup].
pManageDlg->ShowWindow(SW_SHOW) FAILED in [Register Command].
pOptionsDlg->ShowWindow(SW_MINIMIZE) FAILED in [Init].
pManageDlg->ShowWindow(SW_MINIMIZE) FAILED in [Startup].
dlg.ShowWindow(SW_HIDE) FAILED in [Init].
ShellExecute FAILED in CCommandLauncherDlg::OnBnClickedOk with ERROR: 0x2 (ERROR_FILE_NOT_FOUND)
ShellExecute FAILED in CCommandLauncherDlg::OnBnClickedOk with ERROR: 0x2 (ERROR_FILE_NOT_FOUND)
TerminateThread FAILED in CheckIfBusy.
TerminateThread FAILED in CheckIfBusy.
TerminateThread FAILED in CheckIfBusy.
TerminateThread FAILED in CheckIfBusy.
TerminateThread FAILED in CheckIfBusy.
pOptionsDlg->ShowWindow(SW_MINIMIZE) FAILED in [Terminating].
pManageDlg->ShowWindow(SW_MINIMIZE) FAILED in [Terminating].
dlg.DestroyWindow FAILED in [Terminating].
pOptionsDlg->ShowWindow(SW_MINIMIZE) FAILED in [Init].
pManageDlg->ShowWindow(SW_MINIMIZE) FAILED in [Startup].

 

[Doomulation]

Xade & everyone else, can you do this please?
First, DELETE the log before you do something that makes an error so I know what actually happens.
Then, please state what OS you use, also any settings you have (options, keywords), is you use shell integration and start with windows.
For what I can find in that log, Xade, is that sounds fail to play because it can't find the files. Make sure you extract the entire contents of the zip files to a new folder to make sure that all the files are named correctly.
Then I find that somehow the application fails when showing the manage commands dialog with an ACCESS VIOLATION, that is something that would normally crash the application unless I safeguarded against it. But what caused it--I don't know. I need to know more details. I'll also try to enhance the logging function. But for now, try this...

 

[bcrew1375]

Okay, I'm on Windows XP Home. I get the same sound problems as Xade. I'll just use Xade's format here .

- It tried to play the file "greedy.mp4", but it failed. I tried playing it in Quicktime, it tells me it's an invalid file, WMP tells me it doesn't have a codec, though it plays in MPC.

- I also notice the command box is very jumpy when you press F12 or F9. If you press it too long, it pops on and off. You can probably fix that by making sure the key has been released before checking if it is pressed again.

- If I try to use "Keyword It!" with anything, an item flashes on the taskbar and disappears. If I disable sounds, I get a message saying an instance of Quicklinks is already open. If I close the program and try to keyword something, it just opens Quicklinks.

- I have the same problem as Xade with trying to keyword a loaded CD-drive.

- The "Error.log" file is put in the current directory. Was that intentional?

I'll see if I can find anything else.

 

[Doomulation]

About the sound, it plays fine on both my computers, which refers to me that you do not have the required filters to play it through directshow.
I use ffdshow, btw.

About those errors with the shell, I will look into why some fails and some crash. Though I doubt I may be able to make a solution for them. If so, it should simply be added to a known issues section.

I'll fix the error with the log being put in wrong directory.

 

[Xade]

A-hoy,

Just dropping by to check things are going alright. It's probably too late for you to be around now over there, but I hope things are going well with the latest release, bug-wise and the rest.

Get me updated with the latest scoop when you can!

 

[Doomulation]

Much to be done. Experimented a lot lately and been doing other things non-programming.
Some weirdness popping up like that command window staying in the top left corner despite me centering it before showing it. It centers fine AFTER being displayed and centered, though.
Also organizing/changing some code. For example, the shell code was moved to a seperate exe since I couldn't get manifests to work with dlls (that means that plain old UI, instead of the XP one).

 

[Xade]

Yeahhh, I knew about that weird popping up in the corner business...

*Sigh* Here's hoping you get it taken care of. I'm really looking forward to the latest beta!

Ready to fire off yet another report...

 

[Doomulation]

I've been busy lately, as you know. But this new version, although still a little unfinished should fix some things.

Known Issues:

- Options dialog does not have the correct settings when you first run the program.
- If you haven't actually configured any shortcuts yet, you need to at least configure and press "Reset," to actually make them get applied (should only happen the first time you run the application).
- Keyword box isn't properly centered before viewing; I added a hack to center it just AFTER it's displayed.

Should-be fixed issues:

- Commands should now be updated.
- Changed the message for the error with ShellExecute a litte.
- Some special folders like the recycle bin, you will no longer be able to keyword (though I am unsure of the cd drive).

As always, test and see to that you can iron out the most bugs. Meh, 1.0 might just be release on december 24th, if everything goes smooth. A wonderful present, don't you think?

Todo:

- Detect if user keeps holding down the button.
- Fix the disappearing messages (and dialogs) (hiding beneath the current windows).
- Better error logging.

If someone finds that Quicklinks won't run, then please give me your settings, your commands (if any) as well as the path where you put your executable and if you have ALL the files. Please unpack this package to a new folder to make sure that all files are correct.

Also note that to make the shell integration to work, you need to re-enable it in the options.
I have included beta 3 in a .7zip archive to compress it further, and I will continue to do so (because I'm still on 56k at home!). However, in coming versions, I don't think I'll include some unneccesary files (like sounds) to save further space. Meaning you have to extract the contents to your previous installation folder.