Skip to main content
Home Forums Silverlight Programming Report a Silverlight Bug Silverlight... the most handicapped Mouse and Keyboard in history
5 replies. Latest Post by bartczernicki on June 7, 2009.
(0)
Montago
Member
267 points
191 Posts
06-07-2009 3:10 PM |
I find it hillarious that developers need to struggle so much to provide proper control to the user.
- Mouse lacks by design: Mousewheel, Rightclick, Click and Doubleclick event
- There is no real Blur() method on any usercontrol such as TextBox (this means you have to implement an invisible control to takeover the focus)..
a tempoary solution is provided by http://www.sharpgis.net/
The keyboard is just as handicapped:
- Key down and up events are provided, but the browser is somehow more important then the plugin, which means that you have no rights to prevent the event from firering in the browser... F5, F6 and every other function button is grabbed before you get the cance to kill the event. CTRL + [key] is completely related to the browsers already assigned combo's
from my deepest C# heart: ARGGHHHHHH
bartczer...
Contributor
4172 points
730 Posts
06-07-2009 5:46 PM |
Those things are important, it seems though Microsoft is looking at Silverlight 3 to be its next-generation tech with touch/multi-touch input. Like you said we don't have double click or mousewheel, but we are going to be getting multi-touch support in Silverlight with Windows 7 and Windows 7 Mobile. Seems like they skipped a few needed common inputs :)
06-07-2009 6:17 PM |
From a developers point of view - Silverlight API is a FAIL until these things work like they should
06-07-2009 6:23 PM |
@Montago,
I would not classify an RIA API that has full integration with LINQ, can run multiple threads, surface smooth streaming HD media, surface functional langauges, a rich LOB framework etc a FAIL. Which API are you comparing it to? Flash...that still doesn't support secondary threads? HTML..that needs so much hand holding from third party JavaScript frameworks and plug-ins to surface a simple video? Java and its 19 billion projects and assemblies?
There is no perfect API...Silverlight at version 3 (even then its really 2, becuase Silverlight 1 doesn't count) is pretty damn good at what it provides.
06-07-2009 7:15 PM |
i know im being harsh...
and i know that SL is still young and deserves more credit, because it beats the crap out of Flash and Javascript (in advanced features)
but when it comes to simple stuff, i find myself struggleing day after day with half-finished usercontrols which does odd things in relatively simple usecases... and struggleing to get basic inputmethods to work.
remember that Texbox'es only supported USA keyboards in the begining, and no Password boxes... its insane how many hours i've spent on things that HTML has had for so long time...
In my oppinion i think that Microsoft is spending a bit too much time on advanced features, rather then nessecary simple basic stuff like input-methods and basic usercontrols which is needed to convert old ASPX / JS applications ...
although - without my knowledge, they may already be working on fixing all these basic features... i hope so !
06-07-2009 8:16 PM |
I can safely say that Silverlight 3 a bridge release for the Mobile platform. Silverlight 1.1/2 was demo'ed at the MIX conference back in 2007 and again at the PDC 2008. They completely scrapped it, because it wouldn't perform on mobile hardware. They needed 3D transitions, pixel shader effects, bitmap caching, GPU acceleration etc...so it could run on mobile hardware. This is the main reason why in Silverlight 3 we have multi-touch support and don't have mousewheel or double click.
But you are right on that if we don't talk about this stuff we will never see the features added.
Silverlight... the most handicapped Mouse and Keyboard in history