451
N.A.N.Y. 2011 / Re: NANY 2011 Release: JottiQ
« Last post by worstje on December 31, 2010, 02:57 PM »Well, that's when I'll be asleep, so this will have to do. 
Recent Posts
On my pc, I get results going back upto a few weeks though, so let's be hopeful. Keep us informed, okay? 
Just tested a few more platforms (though not requested, but I have them hanging around in VMWare)
Windows Server 2003 R2 32 bit: After installing all prerequisites it all works fine, but there is no Icon displayed in the context menu. But that's a W2K3 setting, AFAIK.
Windows Server 2008 R2 64 bit: Same prerequisited, and the Icon is shown as expected.-Ath (December 28, 2010, 09:09 AM)
worstje, to fix number 2 on your Known Issues list, have a look at AppMutex in the fine Inno Setup helpfile. There's also the CheckForMutexes support function, might you want to check it from some Code.
And here is a way to create it in C# (for if you didn't know).-Ath (December 27, 2010, 02:26 PM)
Just tested JottiQ 0.9.5 on Vista 32 bit.
Guess Vista doesn't like the shell extension, because it's not showing in the context menu of Explorer, or at least not for the files I tried it with. I'll do an uninstall/reinstall to see if I accidentally unchecked that option. [...] And that didn't help a bit, neither when checking the 'Explorer Integration affects All Users' option, so that might need a fix. Vista's UAC is turned off, btw.
This worked fine on 2 of my Win7 x64 setups, one with UAC in it's default setting and one with UAC turned off.-Ath (December 27, 2010, 04:50 PM)
I am surprised it does not work on Vista - it works on XP, it works on 7, you'd expect it to deal fine with the halfway point. Is it the 32-bit or 64-bit variety, or had you got the ability to try on both OSes?Also tested JottiQ 0.9.5 on WinXP 32 bit, but it has the same issue with the context menu as Vista 32 bit has, so it's most likely that that little bugger (the shellextension that is) doesn't behave as it should.
The advantage is that it doesn't want to reboot after a successful uninstall-Ath (December 27, 2010, 05:15 PM)
I've tested it to death myself. Can you explain what you did exactly? Maybe something else went wrong somehow.I can't remember the exact namespace now, but I've easily implemented detection of all running processes in past projects - just a few lines of code. Must be easily found on search engines, or I wouldn't have been able to do it
-kyrathaba (December 27, 2010, 06:04 PM)
IconFilename: "{app}\myicon.ico"
i still dont like the fact that the menu is not going to be fully visible for people without big screens.
changing some of the menu icons+labels to just small icons would fix.
or as i suggested earlier moving the per-item ones to bottom.-mouser (December 27, 2010, 12:54 PM)
After christmas, I intend to focus on the UI and texts and such that I asked peoples opinions on before. I just haven't gotten around to incorporating those details yet.-worstje (December 25, 2010, 02:30 AM)
also, i think a right-click for an item and choosing "perform a google search for this filename" would also be nice.-mouser (December 27, 2010, 12:54 PM)
Would be nice to have an "Uninstall" entry in the start menu group.-mouser (December 27, 2010, 12:50 PM)
)JottiQ
v0.9.5 (2010-12-25)
REQUEST TO TESTERS:
Please test _everything_! Things I need tested in order of priority:
- THE INSTALLER, on all of the below OSes.
- XP 64-bit
- Vista 32-bit
- Vista 64-bit
- Seven 32-bit
For more information, see the official JottiQ (NANY 2011) topic:
https://www.donationcoder.com/forum/index.php?topic=24663.0
VERSION HISTORY
---------------
v0.9.5 (2010-12-25)
It's a special christmas beta-release! Ho ho ho! Merry christmas to all!
Added: Support for Current-User and All-Users installations for the
shell context menu. In essence, this means UAC will no longer be
needed if you install it for your user only. This determination is
made based on the existence of a 'MachineInstallation' file in the
directory the executable is located.
Added: An actual installer! When double-clicked, it performs an
installation that affects your user only. However, if you take the
opportunity to right-click and select 'Run as Administrator', it
will do an installation where it affects all users on your machine.
(And when I write 'it affects', I refer to the shell extension, as
all other application settings are per-user.) A plain .7z archive
will continue to exist for those who like it, however.
Fixed: Shell extension failed to register if it was in a path with
spaces inside of it. Now it works.
Fixed: Windows XP no longer has a butt-ugly clipped shield image when
it needs to elevate to install.
Fixed: Various texts and the likes should no longer be cut off when
running at more interesting configurations involving bigger fonts.
Added: Mnemonics were added to the Settings screen to improve keyboard
accessibility.
Fixed: Changing the shell extensions installed state no longer rushes
through the affair; it now waits for actions to complete so the
Installer doesn't vomit during the Uninstall.
Semi-Fixed: At one point during my own testing on my XP machine, JottiQ
crashed after I clicked a link in the Privacy Agreement screen. I
suspect it involves Firefox demanding an upgrade before continuing;
but I have not been able to reproduce it. So from now on, it should
fail gracefully and spit out an error. If anyone sees this error,
I would be very interested in finding out what it is and whether it
is a common error that needs further looking-into.
v0.9.4 (2010-12-21)
Secret internal beta release.
Fixed: Big booboo involving cached files always returning the same
(very likely unrelated) file results.
Fixed: Windows XP now properly shows the fancy lady bug icon in the
file context menu.
...
KNOWN ISSUES
------------
1) The installer can only delete settings for the current user. This is not
something that I have any feasible way of changing, although I do welcome
any and all suggestions on the topic. This includes the shell context
menu option.
2) The (un)installer does not detect if JottiQ is currently running and offer
offer to close it first. Hopefully will fix at some point in the future.
3) The installer component 'Explorer Integration affects All Users' determines
the creation of the 'MachineInstallation' file. By default it is off,
allowing every user to determine the presence of a file context menu for
themselves (and also avoiding nasty UAC dialogs in the process.) Once
this file is present, one needs Administrator rights in order to turn the
file context menu on or off.
Given point 1), if you install to make JottiQ available to multiple users,
it is recommended to install with this setting turned on so that any
registry pollution stays at a minimum. (Unless of course you are willing
to manually turn off the file context menu for every single user
beforehand.)
4) The uninstaller may tell you to reboot. This is because explorer probably
still has the shell extension in use, and killing explorer and restarting
it is a very user-unfriendly task. As such, postponing the deletion till
reboot time is the user-friendliest alternative.