[Ferο]

The way I'd imagine this working is the small screen inside the case basically another display you'd have to drag the display you'd want on that screen.. Or is there a better more efficient way to do this.

[Xycon]

basically another display you'd have to drag the display you'd want on that screen..

What the fuck does this even mean?

[Gt403cyl]

Basically he wants a small display (similar to a fan controller display) that he can use to display temps and load % on that they can mount inside the case visible through the side panel window.

[datguy.dev]

This can be done fairly easily. However, there are a lot of fine details that you'll have to decide upon or figure out first. There are a lot and frankly it's a bit much to spell out in one post or to someone who doesn't do DIY.

How much do you want to pay for the whole thing?
Do you want to develop for this? Interested in touch screen controls or RGB control?

From a higher general perspective, I see you have 3 realistic options:
1) Use  monitor* like you've explained.
2) Use a RaspberryPi and a monitor*.
3) Use an Arduino Nano and a display, a 16x2 LCD for example.

For plain ole' #1, the first consideration should probably be - how many monitors your PC currently supports and how many your using? Such as you may require to use Displayport to add more displays and being able to extend. Perhaps you have 2 GPUs? Consider, you can buy a separate USB display adapter for the side panel screen. The display: You can salvage a panel and display from something off ebay. Salvage just a drive or panel and purchase the counterpart from an monitor parts reseller. A monitor-like side panel screen is going to be somewhat costly. There are cheap options like the lower resolution 480x640 screens for about $10 that many use for RaspberryPis but often the viewing angle is quite horrendous and they're mostly only HDMI or composite.

Regarding #2, it's soOo much better and cooler to have a standalone system for these types of things. Imagine, it'll boot directly into what it's programmed to do without putting any load on the main system. Many more options to play with. All you have to do is run a script from the main system that send data over serial or the network to the subsystem/display. Such as you can plug an Arduino directly into an open USB header on a mobo for a serial connection. Or you can even use a FT232H to give your PC GPIO to talk with the RPI GPIO.

As I said, there are many ways to skin a cat. If you just want to go the most basic route or can't code, best stick to #1.

Spoiler (Click to View)

[img]http://skpang.co.uk/catalog/images/lcd/823_LRG.jpg[/img]
[img]http://howtomechatronics.com/wp-content/uploads/2015/12/Arduino-TFT-LCD-Touch-Sceen-Tutorial-Example-01.jpg?x57244[/img]

[Xycon]

Basically he wants a small display (similar to a fan controller display) that he can use to display temps and load % on that they can mount inside the case visible through the side panel window.

Yeah I figured that, I actually have one of those myself, I mean more on this part "you'd have to drag the display you'd want on that screen.."
Its something you obviously cant even connect with from inside of Windows or anything .. how are you going to drag anything?

[Ferο]

Yeah I figured that, I actually have one of those myself, I mean more on this part "you'd have to drag the display you'd want on that screen.."
Its something you obviously cant even connect with from inside of Windows or anything .. how are you going to drag anything?

Because it's a small Screen acting as another monitor so you drag the program over to it. Or another thing I was thinking if rainmeter had big enough widgets just put the widgets on that screen.

What do you use for yours?

[Xycon]

Because it's a small Screen acting as another monitor so you drag the program over to it. Or another thing I was thinking if rainmeter had big enough widgets just put the widgets on that screen.

What do you use for yours?

Take your pick.

https://www.newegg.com/Controller-Panels...gory/ID-11

Otherwise, I wish you the best of luck trying to find a screen thats small enough unless you make something as datguy.dev described.

Or just get a second normal monitor and force rainmeter as top layer but move it to the second monitor so you can always see it there and not on the main monitor while you are gaming or something.

[Gt403cyl]

Take your pick.

https://www.newegg.com/Controller-Panels...gory/ID-11

Otherwise, I wish you the best of luck trying to find a screen thats small enough unless you make something as datguy.dev described.

Or just get a second normal monitor and force rainmeter as top layer but move it to the second monitor so you can always see it there and not on the main monitor while you are gaming or something.

I think you took the fan controller bit to literal...

Basically like having CAM info "permanently" displayed.

This is more like what I think they are after...

http://www.overclock.net/t/1581986/therm...-club/1230
http://www.overclock.net/content/type/61...0/flags/LL

Like an actual 6"-8" display that they can use as a second monitor and just keep CAM open on....

http://www.overclock.net/t/1601083/proje...r-ready/30

[Ferο]

I think you took the fan controller bit to literal...

Basically like having CAM info "permanently" displayed.

This is more like what I think they are after...

http://www.overclock.net/t/1581986/therm...-club/1230
http://www.overclock.net/content/type/61...0/flags/LL

Like an actual 6"-8" display that they can use as a second monitor and just keep CAM open on....

http://www.overclock.net/t/1601083/proje...r-ready/30

Yea CAM or something similar I've had friends have issues with CAM that's why I'd try to find something else. If rain meter had big widgets that took up the whole screen I'd put those on that screen rather than turning on and opening CAM dragging it over every time.

[Gt403cyl]

Check this out:

[Ferο]

Check this out:

Hmm pretty much what I had in mind, I wonder if Rainmeter has any full size widgets that would take up most of the screen rather than dragging CAM over.

Thanks!