Rekordbox & Windows 10 Touch Keyboard

Why not? Isn't that kind of standard for apps now? Are there plans to make it touch-optimized?

Because the intention is for the software to be used with a controller, negating the need to touch the computer for the majority of use... and with most computers, there's still a keyboard attached - any "tablet" style computers without a keyboard aren't typically powerful enough to run rekordbox, so that's not really an issue or consideration.

The engineers are aware of the increase in popularity and commonality of touch screens, but again, as the userbase is primarily using a controller with the software, it's a low-priority. The fact it doesn't recognize the field and call-up the OSK should be addressed, so I've passed that along to the planning team.

Make sense!

Like I said, I use it with my DDJ-RZ, and after playing around this morning I am super excited to ditch the traditional laptop and just have a nice slim & discreet tablet in front of me. The Surface Pro 6 is totally powerful enough to run Rekordbox and the DDJ-RZ.

I don't have any desire for the touchscreen capabilities to work with Rekordbox except the text box thing, which should really be considered a bug. Thanks for passing it along.

I totally understand, and hope they're able to address this seemingly simple fix.

Hey @Pulse, just to add an update to this:

I've done a few gigs with my new Surface Pro 6 now, and there's actually another buggy thing that happens with the touch keyboard...

I haven't figured out EXACTLY what I have to touch to make this happen (because it's been in the middle of a gig and I'm not thinking about it), but sometimes I'll "click" something (i.e. touch the screen) in Rekordbox and it will make the touch keyboard pop up when it shouldn't. 

Then, I'll close the touch keyboard (because I don't want it at that point), and following that, anything that I touch in Rekordbox will make the touch keyboard pop up. 

The only solution I've found to making it stop, is to restart Rekordbox, which is not ideal during a wedding reception!

I have been DJing using only touch for a couple of years now. Navigation works as long as you use the moving sidebars for scrolling, but as they are a little narrow (better in RB6 vs RB5) I mainly use the CDJ's or controllers scroll knob for navigation through my collection.

Pulse was your "seemingly simple fix" meant in a sarcastic way?

Cause the cool thing is, to make RB mostly touch friendly, only one thing is needed, and that is in fact a simple fix.

Text input (mostly the search box) needs to give a "signal" to the OS that a text input field has been clicked. The OS then decides based on whether  a hardware keyboard is present to show the onscreen keyboard or not.

Right now, I have to activate the keyboard separately from the taskbar, which is only a small step, but it does make things like using RB6 full screen more problematic.

Also, after activating the keyboard from taskbar, the keyboard keeps being activated when any track is selected. (in other words, RB6 already gives Windows "text input selected" signals, just not at the right moment)

To me this seemingly small fix would make RB6 touch ready.

Of course scrolling in the browser would perfect it, but I guess that's a bigger task and maybe not what you think the devs want to spend their time on?