Plugin DriveInfo

[death.crafter]

Nicely done! Credit to death.crafter, nice skin and to CodeCode for the lua code

I added this to make "Back" easier:
X1MouseUpAction=[!CommandMeasure FileView "PreviousFolder"][!UpdateMeasure *][!UpdateMeter *][!Update]

Ohh, I totally forgot to reply...

Yeah that would make it feel more natural as we do it all the time.

Also, if we tinker around with lua, we can have forward button too. Just a thought, tho I won't be implementing it in the example skin.

[balala]

I added this to make "Back" easier:
X1MouseUpAction=[!CommandMeasure FileView "PreviousFolder"][!UpdateMeasure *][!UpdateMeter *][!Update]

For sure this has nothing to do with the plugin itself, however note that the above bangs doesn't make too much sense this way, because the [!UpdateMeasure *] bang updates all measures of the skin, [!UpdateMeter *] the same way updates the meters, while [!Update] updates the skin itself. If you updated all measures and all meters, why to update the skin as well? Yep, I know updating the skin is not the same as updating all measures and meter, however I still believe (in fact I know well) that using these bangs altogether this way makes no sense. You either should remove the [!Update] bang (and in this case you probably should add a [!Redraw] bang besides the [!UpdateMeter *] as well) or should remove the [!UpdateMeasure *] and [!UpdateMeter *] bangs.

[death.crafter]

For sure this has nothing to do with the plugin itself, however note that the above bangs doesn't make too much sense this way, because the [!UpdateMeasure *] bang updates all measures of the skin, [!UpdateMeter *] the same way updates the meters, while [!Update] updates the skin itself. If you updated all measures and all meters, why to update the skin as well? Yep, I know updating the skin is not the same as updating all measures and meter, however I still believe (in fact I know well) that using these bangs altogether this way makes no sense. You either should remove the [!Update] bang (and in this case you probably should add a [!Redraw] bang besides the [!UpdateMeter *] as well) or should remove the [!UpdateMeasure *] and [!UpdateMeter *] bangs.

Actually, this use is intentional. Since I use things that are relative to each other and need to be updated twice. And things are repeating, so I just used * without hassling with groups and stuff. So I guess I could use two updates, but that would add an extra redraw.

[balala]

Since I use things that are relative to each other and need to be updated twice.

Well, I admit I didn't try out your plugin so far. However I can't imagine a case when the skin should be updated twice.

[death.crafter]

Well, I admit I didn't try out your plugin so far. However I can't imagine a case when the skin should be updated twice.

It's not the plugin actually. It's the meters. I have to make the skin size according to the meters shown. And I have to determine hidden states and stuff according to measures. And some other stuff I don't remember, but they were bugging out due to how the skin is made.

[sl23]

Ohh, I totally forgot to reply...

Yeah that would make it feel more natural as we do it all the time.

Also, if we tinker around with lua, we can have forward button too. Just a thought, tho I won't be implementing it in the example skin.

No problem.

I thought it better to use the X1 mouse button, but the "Back" button is still required, as I imagine there still exist those mouse's that don't have that button.

One thing, this doesn't work for me properly. But this is due to using XYplorer as my default file manager. It captures all folders that are opened in other apps. This seems to include this skin too. So when I click a folder, instead of browsing in the skin, it gets opened in XYplorer.

I know this isn't a fault on your part or Rainmeter. Just thought I'd mention it.

[CodeCode]

Ok. New thing, for the thing I am so obsessed about: Drive Skin!
I know nothing about lua, which is why I was standing off this. But in the view of retaining what sanity I continue to remain in control of - start fresh with a more powerful backbone to this drives thing.
Eventually I will work things out, lots of forum time ahead, methinks.

The first thing I would like to get going is the font the drive names use. Comparison image below. The weird font is actually copy/pasted from artifact ascii that just remains with no real fontface. But I like it, so would love to start there.

Capturez.PNG

[death.crafter]

Ok. New thing, for the thing I am so obsessed about: Drive Skin!
I know nothing about lua, which is why I was standing off this. But in the view of retaining what sanity I continue to remain in control of - start fresh with a more powerful backbone to this drives thing.
Eventually I will work things out, lots of forum time ahead, methinks.

I am using lua for the extra stuff shown in the drives page. Other than that it's all Rainmeter

The first thing I would like to get going is the font the drive names use. Comparison image below. The weird font is actually copy/pasted from artifact ascii that just remains with no real fontface. But I like it, so would love to start there.
Capturez.PNG

Maybe encode the ini file in UTF-8 or ASCII. I can't say anything in particular as I don't know how you got them to show up in your skin.

[CodeCode]

I am using lua for the extra stuff shown in the drives page. Other than that it's all Rainmeter

That's cool. It will make more sense to start with. As I learn how to get around this lua script.

Maybe encode the ini file in UTF-8 or ASCII. I can't say anything in particular as I don't know how you got them to show up in your skin.

Ok, lol. This is pretty geeky stuff so here goes.
This is the Link
I used this all the time is discord, then one weird day, I thought to try it in my drive names. So in the windows folder the drives look exactly like them in the example above. As if by magic, I noticed the drive names in my rainmeter skins were inheriting that font. Ever since its been like that.

[CodeCode]

Hello.
After realizing what I actually did, by modifying your driveinfo skin, I went back to the Titan Drives base and added the necessary sections etc that I needed.

I am now trying to implement and integrate the lua script's advantages to enhance Titan's functionality.
This bit of code is meant to retrieve all the specs of each drive:

Code: Select all

[DriveSpace1]
Meter=String
X=r
Y=15r
FontSize=8
StringAlign=LeftCenter
Text=[&pName:GetSpaceLabel(1)]
MeterStyle=Contents
Hidden=(1-[&pName:IsDrive(1)])
DynamicVariables=1
Container=Container1

The output is literally what is in the Text option. So I surmise that there is a dependency for that to get the info rather then the literal string.

I dont really know where to look.
These are in the ini as well:

Code: Select all

[Label]
Measure=Plugin
Plugin=DriveInfo
Drive=G
Type=FileSystem

[pName]
Measure=Script
ScriptFile=#@#Scripts\TitanDrives.lua

So I am missing something for this purpose.
Any help is appreciated.