Quote:You'll find the mouse-actions there as well. However - that is the pure file of available actions, not indicating what they actually do.
:-)
Sorry. I can't help but snicker a little at this comment. I mean it isn't as if the material in the wiki... in particular
this page which is supposed to document actions... make any serious effort to describe the actual semantics for any of the built-in actions of XBMC.
Quote:I think that it simply doesn't make a whole lot of sense to even think out the actual mouse-options one might have with the different mouse-devices you get on the market since the mouse can be considered way to sensitive to work with a media-center. It also doesn't make a whole lot of sense (to me at least...) to try to control a media-center with a mouse-device.
Well, as my father used to say "If you are going to do something, do it right." That's my feeling.
Clealy, XBMC already has
some level of mouse support. And as I've said, I think that is a damn good thing because that is how
I personally find it most easy to control the thing... even from 10 feet away on the couch... perhaps even
especially from 10 feet away on the couch. So the question isn't whether XBMC should or should not support mice as an input/control device. That Rubicon has already been crossed. Now the only question is: Shall mouse support in XBMC be done in a rational, sensible, and complete manner, or shall it just be left sort-of half baked? My own opinion is that the former is better than the latter.
Let me ask you this... I don't know my way around either XBMC or Confluence very well at all yet, but I
have had to ``
add media sources''. When I have done this, a little keyboard-like thing has popped up on the screen, allowing me to enter the pathname of the new source and also the identifier that I wish that new source to be known by, i.e. when it is displayed in a list of possible media sources. Have you seen that? I assume so. So tell me please (because I really am interested) how does one enter those strings when all one has in hand is a TV-type remote control (with no alpha-numeric keyboard)?
With a mouse in hand, entering this data is easy using the on-screen keyboard. With just a remote in hand however I'm not sure it can even be done
at all.
This all having been said, let me assure you that I
do understand your point about not wanting to waste limited resources of Team XBMC, but I wasn't really proposing any big investment on their part. I was thinking that I'd try to do the coding & initial testing myself, and then they would just have to review, approve, and integrate. I certainly was
not expecting anybody from Team XBMC to drop everything and rush over to start improving mouse support just because this one newcomer said how much he liked mice.
Finally, regarding your point that some (many?) skin don't currently support mice... either well or, perhaps at all... I have a simple response... So what? Looking at the "standard" Confluence skin, it appears to me... and please correct me if I'm wrong... that it only supports 720p output devices. If true, where does that leave people who want to use Confluence on their iPhones?
XBMC is skinnable. Some skins work better with some kinds of hardware than they do with other kinds of hardware. It seems to me that there is nothing wrong with this. It is what it is.
Quote:Am i the only one who thinks that ronbaby is just ranting in a cloaked arrogant way?
To the charge of "ranting" I plead guilty.
I'm not sure how anything I've said could be considered "cloaked" in any sense. I mean it's all been posted right out here in public and I've meant what I said and said what I meant.
As regards to the arrogant part, I have no way to judge that. Arrogant in what way?
P.S. What (or who) is SDL?