slimCODE, aka Martin Plante

Referencing a debug assembly in debug builds, and a release assembly in release builds

slimcode — Fri, 12 Jun 2009 05:29:41 GMT

I have a few VS.NET 2008 projects that share usage of libraries I made for Windows Mobile. I used to include the libraries’ projects directly into each solution, but this is leading me to rebuilding those libraries each time, even if the sources do not change often. It also could cause two applications to look like they’re using the same build of those libraries, while they’re not actually the same bits.

So I decided to move those libraries outside my solutions, and have a separate build for each. Now, I still wanted to reference the debug builds when building the debug versions of my applications, and the release builds when building in release. Turns out you can hack into your project files to accomplish exactly that.

Open your .csproj files with a text editor and locate your references. They should look like this:

<Reference Include="slimCODE.slimCONTROLS, Version=1.0.9312.0, Culture=neutral, processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>
<HintPath>..\..\Binaries\Release\slimCODE.slimCONTROLS.dll</HintPath>
</Reference>

There are two ways to make the above reference change target based on the active configuration.

Add a condition

You can add a “Condition” attribute to the <Reference> tag that will make that reference toggle based on that condition. It can be anything. In our case, it would look like this (important stuff in red):

<Reference Include="slimCODE.slimCONTROLS, Version=1.0.9312.0, Culture=neutral, processorArchitecture=MSIL" Condition="'$(Configuration)' == 'Release'">
<SpecificVersion>False</SpecificVersion>
<HintPath>..\..\Binaries\Release\slimCODE.slimCONTROLS.dll</HintPath>
</Reference>
<Reference Include="slimCODE.slimCONTROLS, Version=1.0.9312.0, Culture=neutral, processorArchitecture=MSIL" Condition="'$(Configuration)' == 'Debug'">
<SpecificVersion>False</SpecificVersion>
<HintPath>..\..\Binaries\Debug\slimCODE.slimCONTROLS.dll</HintPath>
</Reference>

Thus, for each reference you want conditional, you must add a second entry for each subsequent configuration name. Don’t forget to change the <HintPath> accordingly.

Cheat the hint

Turns out the <HintPath> can contain variables, like $(Configuration). That’s an easier way to redirect to the proper build, given your binaries are located in folders using the configuration names. That was my case.

<Reference Include="slimCODE.slimFORMS, Version=1.0.9312.0, Culture=neutral, processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>
<HintPath>..\..\Binaries\$(Configuration)\slimCODE.slimFORMS.dll</HintPath>
</Reference>

Though the first way looks more Kosher, the second way seems to behave correctly too, is simpler, and adapts automatically for each new configuration, given you use the correct folder names. Changing the active configuration does make the reference’s “Path” value in the “Properties” window change accordingly.

I’ll try both and give you more feedback if one fails.

slimKEYS is now free - Why?

slimcode — Wed, 06 May 2009 13:49:52 GMT

In case you haven't heard yet, slimKEYS is now free to use. Totally free. No catch, No ads, no malware, nothing.

Why would someone earning money from a product decide to make it suddenly free?

Because I never made any money with slimKEYS.

Now, you're probably thinking "slimCODE decided to make slimKEYS free so they can stop putting energy on it", right?

Is this the end of slimKEYS?

No way! For a simple reason: I'm the number one customer myself. I couldn't work on a computer without slimKEYS.

Then, why not leave it at 15$?

Because I still dream of seeing slimKEYS becoming a successful product, and I realize my definition of "successful" isn't based on the amount of money I can bring in with slimKEYS, but more with the number of users I can gather. The equation is obvious:

I'll never make a fortune with slimKEYS, never.
I want to continue to work on slimKEYS.
I need motivation in order to work on a product.

So my last attempt in keeping motivation is to make it used by more and more people. And for that, I'll need help from the current very loyal users. Spread the word! Blog it, tweet it! slimKEYS is free, and there's no catch.

And if people still think it deserves money, it's always possible to make donations.

And besides, if I can't make money with it, why not drive traffic at least?

But I paid for slimKEYS! That's not fair!

I agree, it's not fair for those who paid. If you really feel betrayed, you can ask a refund. If you really think that back then, slimKEYS was worth something, but now it doesn't, even some small donation, I'll gladly refund.

Just send me an email with your registration information.

Why not make it open source?

The answer should now be obvious: I still want full control and ownership of the hard work I've put into slimKEYS. Else, motivation would drain away a little more. Starting an open source project is a logical pattern. Turning a 4+ years old project into open source is resignation.

Maybe one day. Once the user base is strong enough? Maybe.

How do you pay your bills, then?

I hope this does not surprise you, but slimKEYS is not my only professional activity. I do contracts for custom development, and I also work on other product ideas (too many, must focus!). I'm leaning toward mobile development. For example, I have slimPASSWORD for Windows Mobile coming soon, for opening your slimLAUNCH.Passwords file on your phone. I also have two other Windows Mobile apps in the oven.

As for DutchTab for Windows Mobile, still at 5$, it will also become free in a few weeks, with a small update. I don't think my two customers will mind.

slimKEYS v1.4.9255 is released!

slimcode — Wed, 06 May 2009 13:46:56 GMT

A new version of slimKEYS was released yesterday. The main two new features involve slimSIZE and slimVOLUME, in somewhat related features.

New with version 1.4.9255, you can tell a slimSIZE hotkey to grow or shrink a window, instead of only forcing a specific size.

In a same thinking, but opposite result, you can now create slimVOLUME hotkeys that set the volume to a specific level, instead of just increasing or decreasing the level. For example, I created myself a Win-VolumeUp hotkey that fixes the volume level to 50%, and another Win-VolumeDown that fixes it to 5%.

Other than those two features, a small change to how the slimLAUNCH window behaves when you type alternate shortcuts. For example, when a FileSystem item is selected, you could press Ctrl-F to open its parent folder. According to my own SDK documentation, the implementation should have made the slimLAUNCH window close, but those were only words. Now it does close the window.

Oh, and another small detail: slimKEYS is now free!!!

(more on this in a following post)

I'm an HTC Touch Pro fan... but why a Pro2?

slimcode — Mon, 16 Feb 2009 14:28:54 GMT

I'm an HTC P4000 owner, and I really like having a phone with a sliding keyboard. I had my eyes on the new HTC Touch Pro for a couple weeks now, but I just noticed (via @wmdev) that HTC released a second generation Touch Pro, called Touch Pro2 (what did you expect for a name?). I have nothing against multiple generations, they are a sign a company is evolving and improving. The Touch Pro was available since only a couple months. Why release a Pro2 so early? Is the first gen buggy? Is there something we should know about it?

Looking at the sales pitch for the Pro2, it looks like the only improvement is the conference call features. It's about the only thing they brag about. I decided to compare both specs to get a better glimpse at the differences.

The Pro is smaller in width and height (102 x 51 mm) than the Pro2 (116 x 59 mm), but is actually thicker (18 mm versus 17.25 mm), which is not apparent when looking at photos.
The display screen is way bigger on the Pro2, at 3.6" instead of 2.8". This enables a better resolution of 480x800 (WVGA) on the Pro2, versus the 480x640 (VGA) resolution for the Pro.
The Pro2 is slightly heavier at 175 grams, only 10 more than the Pro at 165 grams. But with a bigger body and screen, that's expected.
The Pro2's sliding screen can be tilt for better viewing.
The battery in the Pro2 has a 1500 mAh capacity instead of 1340 mAh for the Pro, but with a WVGA resolution to drive, it shortens the Pro2's use time on WCDMA networks from 378 minutes to 270 minutes (that's a lot). Strangely, on GSM networks, it's the same for both devices (I don't get it).

The rest is about the same. 512 MB ROM and 288 MB RAM, almost the same Qualcomm processor at 528 MHz (7200A for the Pro2, 7201A for the Pro).

HTC should really push more the fact it has a bigger screen and better resolution. Those are far more important features for me than conference calls. I was preparing myself to buy a Touch Pro so that I could play with G-Sensor development. I think I'll wait for the Pro2!

Fixing error code 29506 when trying to install SQL Management Studio Express

slimcode — Fri, 30 Jan 2009 18:15:00 GMT

Like many others, I was getting an error code 29506 when trying to install SQL Server Management Studio Express 2005 on my Vista x64 machine. Searching for a fix kept sending me to posts talking about running the MSI as administrator from the beginning, but this didn't solve it for me, neither did it solve it for many other commenters out there.

The good news is, I did find a solution! And I bet that if you end up reading this post because of a similar error, we have something in common: we downloaded the MSI using Internet Explorer 7 (or 8)! The file gets stamped as "coming from the net", thus has restricted privileges, even when running it as administrator.

Simply right-click the file and select "Properties". At the bottom of the "General" tab, you should see a security message with an "Unblock" button:

Pressing that "Unblock" button will remove metadata associated with that file. Running the MSI again should now work fine, even without running it from an administrator prompt, but I did ran it from an admin prompt just to make sure.

Update: As many commenters mentioned, you still need to execute the MSI from an admin command prompt.

Hope this helps!

Babies Know

slimcode — Wed, 28 Jan 2009 13:30:28 GMT

I got this by email yesterday. It was too good to leave as an email... And I'm against an email chains, so better start a Twitter chain! ;)

And

Another slimKEYS release, v1.3.9063

slimcode — Wed, 14 Jan 2009 21:54:27 GMT

There's a new slimKEYS release around town, version 1.3.9063. Why the "3" in "1.3"? Simply because there was a minor change in the plug-in programming interface, and I'm a purist. But I'm not ashamed of increasing the minor version number, since there's also a new plug-in: slimZOOM.

The default hotkey is Win-A. Move the mouse over the area you wish to zoom in, and press the hotkey. A zoom window will appear. You can press W to toggle the window to use a full monitor or your whole display (yes, for single monitor systems, that's the same thing).

There are many other options, I'll let you play with it to learn more (or watch the demos). As usual, many other small things have been fixed or improved, but one thing worth mentioning is the ability to rename hotkey descriptions to use your own.

Have fun with this new release, and thank you all for the suggestions and bug reports. I'm listening, and I'll continue working on very nice suggestions received on the forums and by email.

Souvenir of a PDC

slimcode — Mon, 03 Nov 2008 15:11:33 GMT

I’m back from PDC 2008, sitting at my computer, trying to apply in more concrete ways what I’ve learn there, and evaluating how this will affect my projects in the near future. Indeed, Windows Azure was a great announcement, and seems a great platform, though I haven’t worked with it yet. During the PDC, what seems a great product idea popped up in my mind, and Azure will be the target platform for that idea. But it’s only out off laziness that it won’t be implemented on Amazon or Google platforms. Again, Microsoft is making sure developers are comfortable, have a great - scratch that - an awesome development platform to work with, so they make their technologies de facto in the industry.

But Azure was expected, written in the sky, the next logical move from Microsoft to address the concurrence of Amazon Web Services and Google Apps. It was even a platform they needed themselves for their web-page app offerings (e.g. Office 14 Web). I wasn’t going at the PDC to learn more about what was being that Mesh thing, but to learn more about the two Windows 7 that they are cooking for us, the desktop and the mobile.

The first one was a very early glimpse, with cool UI features, but we didn’t learn much of the inners. Ok, we’ll get touch APIs, that’s great. The “libraries” view is a good way to make us forget about one of the three pillars of Longhorn that was dropped after PDC 2003: WinFS. It’s a simple interface with a simple API, which will do the work for a while. But let me give you a good example why it’s still not enough: This morning, my wife needed a picture of Clément to upload to a web site. She doesn’t exactly know where our pictures are located. So opening the “Browse” button on that web site turned out to be quite an adventure for her. Once I told her pictures were in “K:\Photos”, she faced a second problem: She couldn’t browse pictures by tag or date like she’s used to in Windows Photo Gallery or Picasa. She had to open each folder one by one, change the view to see bigger thumbnails, remember paths of interesting pictures while she browsed other folders. Then I told her to open Windows Photo Gallery, find the correct picture, right click it and select “Open File Location”. Ok, great! She ends up in a folder containing 150 pictures, the correct one being selected. All filenames look the same (PICT####.jpg), but she can’t copy that file’s full path, only its folder path. Back to the web app, paste the folder path (which is already a power user action in my book), and search for that filename. Painful.

This experience really made the cool “libraries” section in Windows 7 become much less cool in my mind. It’s still not enough. The normal computer users need an operating system that does not talk to them in terms of paths, but really in terms of properties. It was time for this shift in 2003, it’s even more pressing now.

For the moment, Windows 7 is simply an improved Vista, which is not a bad thing. I like Vista, call me crazy if you want, but I live very well with the various UAC and warning prompts. Sure, having less of them will always be welcomed. But it’s still a necessary evil. Ubuntu has them, Mac OS X has them, Vista simply needs to reduce their occurrence. The simple fact that a file downloaded from the net causes two prompts is the single most important aspect the Windows 7 / Explorer / Internet Explorer teams must address. Then a few other Explorer annoyances, and the UAC subject will be almost closed. But Windows 7 wasn’t such a big news at this PDC.

The other Windows 7 is one very important stone for Microsoft. They have addressed a “corporate developer” need in Windows Azure, but have neglected the Windows Mobile platform (at least in our eyes, I’m sure that team is working hard). Why? Too “general user”? Wake up! The iPhone is a corporate success too. I saw more iPhones than Blackberrys at this PDC, in the hands of professional developers. And I saw more non-Windows Blackberrys than any Windows Mobile devices combined. Their smaller Windows 7 needs love too, but it’s not at this PDC that it received a hug. The foundations of Windows Mobile are strong. It is a serious operating system with a rich API, which is unfortunately often its biggest flaw. Developers don’t program well for this mobile platform. They use too many resources, apply practices learned from the desktop, do not behave well in this multitasking, application switching context, because they still don’t care about being the active application or not. Hey, it’s not important on Windows, why care about it on Windows Mobile?

So, what is missing from Windows Mobile? A serious development platform, paradigm, framework. As of today, the Microsoft offering for developing for Windows Mobile can be resumed at two things: Normal Win32, or .NET WinForms applications. In the first case, you’re faced with the desktop way of developing. In the second case, you’re told to work with that obsolete technology that is not good enough for the desktop, and does not apply well to the mobile world anyway. WinForms is a “one form per screen” framework enforcing the notion of a main form. What happens on Windows Mobile when a form opens a child form? You see it twice when you switch between applications. I had to create my own framework based on UserControls to create something more appropriate to the device.

Then comes what you put on those screens. Windows Mobile gives us the same old controls we have on the desktop, but uglier. The control set on Windows Mobile should be placed in a museum. It is useless when you want to create interfaces that work well with touch devices. Wake up, Microsoft! People can work really well on their iPhones without the need for a pen. I’ve seen people type on their iPhone faster than me on my HTC P4000, even if I have a sliding keyboard. You need to upgrade the user experience on Windows Mobile. And just like you do so good on the desktop, you need to make developers comfortable to develop for it, so their laziness becomes your number one weapon.

I went to PDC 2008 with the naive intuition I was in for a great surprise about Windows Mobile. I spent 3200$ (PDC + Hotel + Plane) out of my own pockets to be there. What a mistake. The only thing I officially learned was that Silverlight would work on Windows Mobile. But I have no bits to work with yet, and no serious information of how (and if!) it will work as a stand-alone client-based solution. During the various keynotes, we kept seeing the same slide showing the three important areas for Microsoft: The desktop, the web and the phone. But we heard nothing, “nathing”, of that last piece of the equation. Then, on the Ask The Experts evening, when I finally found the Windows Mobile table (which was not where the plan said it was), I could not get any answers, the team clearly bound by a non-disclosure thing. I could only understand, by their smiles and shoulders, that something was coming, but my 2200$ PDC ticket was worth nothing when it was time to learn about it.

So, this morning, I’m in front of my computer, wondering how I should spend my energies toward the Windows Mobile platform and my future projects, and I have no answer. 3200$ later, I’m at point A. Worse, anybody can watch all the sessions for free, just by visiting Channel 9. What a slap in the face! That Cocoa thing looks interesting. I heard their documentation is awesome. Maybe that was the price to pay to learn it the hard way?

Technorati Tags: PDC 2008,Azure,Windows 7,Windows Mobile

PDC 2008 – Day 1

slimcode — Tue, 28 Oct 2008 03:11:02 GMT

So day one of PDC 2008 is coming to an end, I’ll be going to the “Show Time” special session in a few minutes, then check if there’s a party around. What did that first PDC day bring me exactly? Well, I can now put a name on something obvious that had to come from Microsoft: Windows Azure. The cloud finally has a name… a better name, that is. I’m still wondering if they did tie the “Operating System” tag to Azure strongly enough. Because that’s what it really is. I kept saying that Live Mesh had to be more than just synching and remoting. Turns out it is only a part of the bigger Azure picture.

Azure is a good thing for Microsoft. A very good thing, because Microsoft has the developer framework to succeed. They’ll end up doing much better than Amazon or Google, because devs feel very comfortable with the whole Visual Studio echo system.

The down side is: that wasn’t a very exciting day. All this was expected news, obvious news, the normal path MS had to take to consolidate corporate developers they had a little neglected in the past years.

Now, it doesn’t mean the “end user” developer must be neglected now. I’m very eager to see tomorrow if the "Other Windows 7” (Mobile) will have his period of fame. The future of Windows Mobile is much more than simply running Silverlight stuff natively on mobile devices. The interface needs a facelift, and the developer community around Windows Mobile needs more support from Microsoft itself. The other reseller players in the industry are doing terrible damage to Windows Mobile’s image. They suck! It’s great to see more APIs, but Microsoft is not just an API company. Enough ingredients, let’s make some recipes. Let’s bring something like the Apple App Store to Windows Mobile. Only Microsoft can make this happen successfully.

Technorati Tags: pdc08,Azure,Windows 7,Windows Mobile

Free slimKEYS license if you see me at PDC 2008

slimcode — Mon, 13 Oct 2008 21:08:07 GMT

Update: I will use a special PDC badge instead.

I’ve decided to give away slimKEYS licenses to anyone who recognizes me at the next PDC 2008 in Los Angeles. That’s right, free as in beer. Just watch carefully for me and my PDC Badge, in case it reads like this:

Simply stop me and ask for your free slimKEYS license. If you’re curious, you can even ask me to show you what slimKEYS can do for you.

But if you don’t see the badge above, no candy! ;-)

(Maximum of 1 free license per person, no purchase necessary, only valid between October 26th and October 31st, this contest is NOT void in the province of Quebec (!), participants must sing this song in order to claim their price… just kidding!)

See you at PDC 2008!

Technorati Tags: pdc08,slimKEYS

FirstPen – For children to practice handwriting

slimcode — Wed, 08 Oct 2008 14:54:44 GMT

My son Clément really likes computers and Pocket PC devices. More than pens and papers. I even gave him my old HP Jornada 545. He’s also having some difficulties with handwriting and precision. So I thought I’d use that attraction to my Windows Mobile phone to make him practice a little. I made an application, called FirstPen, for practicing handwriting.

The idea is simple. You must complete the gray outline the best you can, without drawing outside. After each letter, the application calculates how well you did it.

This is a first draft, and I need feedback to make sure I’m on the right track. For example, a feature not yet implemented would be to make sure letters that must be done in a single or two strokes are made in a single or two strokes. Another one would be to make sure letters are started at the correct position.

I’m also looking for fonts that best match how children learn to write at school. It seems every font I find has its flaws. Here are the fonts I’m currently supporting:

As you can see, some of them do not support accented chars, which is a problem for me, but isn’t for English users. Others have guiding lines. This can be very useful, but in order for my precision algo to successfully determine if a letter is well done or not, the letter to draw must be gray, and other decorations must be a lighter green or red. That’s why I must manually edit each letter to make those guiding lines green, like this:

This is a painful task I’d really like to get rid another way, but since I like the idea, I’ve completed the “DR BY 2” font as a proof of concept. This also opens the door to green helpers, like arrows for direction.

So, if you want to try this out yourself, upload this CAB file to your Windows Mobile device, install it, and give me your impressions. I do not intend of charging for this app. If it grows better with your feedback, everybody will benefit from it, for free.

By the way, the CAB file is 3 megs because of the embedded images, but I haven’t run PNGCrush on them yet. It should get smaller. Please note that it also requires the .NET 2.0 Compact Framework. It should work on Pocket PC 2003 devices, and Windows Mobile 5 and 6.

Technorati Tags: FirstPen,handwriting

slimKEYS v1.2.8479

slimcode — Thu, 02 Oct 2008 21:15:04 GMT

Today, I released a minor update to slimKEYS, version 1.2.8479. The three most important new features are:

slimSEARCH: You can configure any web search entry to replace spaces by a specific character instead of the default “+”.

This is particularly useful for Wikipedia and Wiktionary searches, since those web sites require spaces to be replaced by an underline (“_”). As a matter of fact, the first time you run this new build, slimKEYS will automatically set this option “on” for entries pointing to “wikipedia.org” or “wiktionary.org”. If you have similar issues with other search targets, you’ll have to manually change them.
slimLAUNCH.Passwords: When managing password stores, you can rename categories and entries right from the tree view, and even drag and drop entries from one category to another.
slimSMOKE: You can tell the hotkey handler to cycle through all combinations of dimming/blurring/off, instead of simply turning it on and off. Thus, when enabling this option, pressing Ctrl+Win+M actually changes the slimSMOKE status to:
- Dimming + Blurring
- Just dimming
- Just blurring
- Off

Another important change is regarding the trial message. Before, a notification pop-up appeared every 15 hotkeys you pressed. Now, every window will show a small clickable message at their bottom.

Rest assured, there is no time bomb in slimKEYS, and there will never be. If you like slimKEYS, but do not think it is worth 15$, you just have to tolerate this red message and ignore the end user license agreement… but don’t tell me! q;-)

For the rest of the changes, take a look at the complete history. By the way, how do you like the new web site look?

DutchTab is out of beta!

slimcode — Mon, 04 Aug 2008 20:28:45 GMT

DutchTab for Windows Mobile is out of beta, and now officially supports both Pocket PC and Smartphone devices running Windows Mobile 5 or 6. This application is a joined venture with my friend Pascal who made an iPhone version of DutchTab at the same time I was working on my Windows Mobile version.

This application is a bill-splitting tool, but does not limit itself to making simple divisions. It automatically calculates who owes who depending on everybody’s contribution at the moment of paying the bill, and also the cost of their purchase. For example, your team is ordering lunch at the office, but the delivery guy comes in with a single bill. It adds up to 53.34$, Steve gives 35$ and John gives 25$. Mike and Lisa didn’t have cash. Now who owes who? You think it’s as simple as dividing 60$ by 4? But Mike took the expensive ribs, while John went for a simple salad. It wouldn’t be fair. Now, how do you split the tip? And when comparing the meal prices with the total amount paid, you also have to consider the taxes.

No problems. Steve is a wise man. He kept a copy of the bill, and uses DutchTab to enter that bill. He creates a new bill:

The bill is new and empty. It’s time to add partakers:

DutchTab will show you all previous partakers, and lets you either add new entries manually, of quickly import them from your Outlook contacts:

Steve paid 35$, and took the chicken and a Sprite:

Lisa went for the finger-licking chicken fingers (with the honey-mustard sauce):

John paid 25$, took a salad for his line… and a Coke because a salad is not enough:

Finally, Mike got the famous ribs and a Coke, nobody’s complaining about his line… yet!

Now, on the bill’s summary, we can see that the total before taxes and tip is 49.85$. Steve entered the prices as they appear on the bill. No need to add the taxes, DutchTab will take care of distributing the taxes and tip proportionally.

DutchTab determines that Mike’s meal, with taxes and tip, was worth 20$. Since he paid nothing, the application tells him he should give Steve 20$. As for Lisa, her meal’s total price was 13$. She owes John 12$ and Steve 1$. Steve can now click on “Send email” to send everybody a nice reminder.

I hope this gives you a good idea of how useful DutchTab is.

Technorati Tags: DutchTab

DutchTab is now available

slimcode — Sat, 12 Jul 2008 21:05:19 GMT

What is DutchTab? It’s a Windows Mobile application I’ve been working on for the past weeks. My friend Pascal Bourque convinced me (pretty easily) to migrate an application I made years ago for splitting lunch bills at Xceed. We decided to make that a shared adventure, him making an iPhone version, and me the Windows Mobile version.

The idea behind the software is very simple: You enter how much each person actually paid, and also the cost of what they bought. The software automatically calculates who paid too much and who didn’t, and optimally determines who owes who.

The number one challenge was that we didn’t share design, only the name. We headed in our own direction and waited only a few days before release before sharing a few screenshots and screencasts. We did make some adjustments, mostly wording, but kept each application’s personality. I really think this was a wise decision. Both platforms have their own design guidelines, and both devices have their own input methods. I’ll add that Pascal had the easiest part, since the iPhone does not have zillions of buttons. He could concentrate on touch gestures and actions, while I wanted to support buttons and touch screens. My goal is to run on both PocketPC and SmartPhone devices, but the current beta release fails on SmartPhones because I’m using an unsupported feature with combo boxes (dah).

You can learn more about the Windows Mobile version of DutchTab here. This initial release is a beta version, and I’ll be offering those who submit meaningful comments a free license once I release the official version.

Technorati Tags: DutchTab

slimKEYS 1.2.8310 now available

slimcode — Tue, 10 Jun 2008 14:26:47 GMT

A new version of slimKEYS is now available. Though the list of new features is slim, it took me more than just a few hours to get through translation of the interface to French, and to finally make slimVOLUME support 64-bit Vista systems.

In the first case, it was a long and tedious job of moving every string to a resource file, translate each one, localize each form and repeat the translation for each label. It was simply long, and boring.

In the second case, I had a problem. Taking apart the numerous p-invokes throughout the code (but mostly in slimSIZE), slimKEYS is a fully managed C#-made application, except for one tiny portion of code used by slimVOLUME. The slimCODE.slimVOLUME.Vista.dll file is a mixed assembly made in C++. Normally, .NET applications don't have to care about the address space size. 32-bit or 64-bit systems don't matter, as long as the CLR implementation on both platforms is equivalent, and that your p-invoke signatures are correct. But in the case of slimKEYS, when the 64-bit implementation of the CLR was trying to load this mixed assembly, it caused a load error. An unmanaged 32-bit application can run flawlessly on 64-bit systems, but a 32-bit DLL cannot get loaded in a 64-bit CLR domain.

Usually, unmanaged applications that wish to natively support both 32-bit and 64-bit systems offer two packages, each built exclusively for each platform. But that's totally against the logic behind managed applications. At least that's what I thought. It was easy for me to build two versions of my C++ DLL, but how could I use them from a single managed application? How could I keep offering a single and consistent package?

After investigating, asking questions without getting precise answers and doing some trial and error, I chose a solution that isn't guaranteed, but seems to work well. My C++ DLL implemented a single class, called VistaVolumeControlsBridge. The managed plug-in declared a base class named VolumeControls, with two derivatives VistaVolumeControls and WmmVolumeControls. So there was already a level of indirection, where the VistaVolumeControls class was instantiated based on the platform, and using an instance of VistaVolumeControlsBridge under the hood. What I did is create a 64-bit version of the C++ DLL which implemented class Vista64VolumeControlsBridge, and its Vista64VolumeControls counterpart on the managed side. Now, the decision between creating a WmmVolumeControls or a VistaVolumeControls based on Environment.OSVersion had become a three dancers decision that looks like this:

      if( Environment.OSVersion.Version.Major >= 6 )
      {
        if( IntPtr.Size == 8 )
        {
          m_volumeControls = new Vista64VolumeControls();
        }
        else
        {
          m_volumeControls = new VistaVolumeControls();
        }
      }
      else
      {
        m_volumeControls = new WmmVolumeControls();
      }

Since VistaVolumeControls and Vista64VolumeControls are themselves managed classes, this doesn't seem to trigger loading of the 64-bit type on 32-bit systems by the JIT, and vice-versa. I could not find any reference if I could assume that a type that is never instantiated will never require its containing assembly from being loaded. But I'm ready to take the risk, and wait for your feedback if it breaks.

Another neat feature with slimVOLUME on Vista is that you can now change which playback device's volume you are controlling. I also wanted to change the default playback device with a hotkey, but Microsoft doesn't want this to happen. They think device manufacturers would abuse of such an API to make their hardware stay always as the default device. And I'm not making this up, I read it on their forums (here, here, here and here), and asked Larry Osterman myself:

We've gone around and around on this one, and while at some level it would be nice to allow developers the ability to change the default audio device, there is no way that we can. The problem is that audio vendors would abuse the functionality to attempt to force THEIR hardware to be default device even if the user didn't want it to be (we've seen evidence of vendors doing this in the past).

We used to say something at Xceed about those situations: Two wrongs don't make a right! This is a very good example. Creating a problem to avoid another one. I really think it was a stupid decision. Changing the output device on Vista requires 4 steps:

Right-click the speaker tray icon.
Click "Playback Devices".
Right-click the device.
Click "Set as Default Device".

Failed.

I'd be really happy to see an API for this in Windows 7. But if there are hackers reading this, can someone tell me what is called under that "Set as Default Device"? The API already exists, it's just not documented.

Tags: slimKEYS, slimVOLUME