balala wrote:I don't think that the described behavior would be a bug, nor of the InputText plugin, nor of the skin. Simply the plugin doesn't support line breaks, because hiting enter determines the plugin to execute the appropriate command, instead of creating new line.
CTRL-Enter will work to create a line break in the input, but don't forget that you now have two lines, and unless the defined input box is tall enough, the first line is going to be visibly pushed out of it to the top, and although it's there, (just scroll around with the arrow keys while inputting to see what I mean) you won't see it.
In any case, there is no bug. CTRL-Enter works exactly as expected, and creates a line break in the input.
Code: Select all
[Rainmeter]
Update=1000
AccurateText=1
DynamicWindowSize=1
[MeterSearchBox]
Meter=Shape
Shape=Rectangle 1,1,202,25 | Fill Color 215,215,215,255 | Stroke Color 130,130,130,255
W=202
H=25
LeftMouseUpAction=[!CommandMeasure "MeasureSearchInput" "ExecuteBatch 1"]
[MeasureSearchInput]
Measure=Plugin
Plugin=InputText
X=4
Y=3
W=188
H=22
SolidColor=200,200,200,255
FontColor=47,47,47,255
FontSize=11
AntiAlias=1
FocusDismiss=1
UpdateDivider=-1
Command1=[!Log "$UserInput$"]
That will move the first line up text up so it won't be visible anymore when you hit CTRL-Eneter, as it has only enough room for one line in the input box.
Code: Select all
[Rainmeter]
Update=1000
AccurateText=1
DynamicWindowSize=1
[MeterSearchBox]
Meter=Shape
Shape=Rectangle 1,1,202,50 | Fill Color 215,215,215,255 | Stroke Color 130,130,130,255
W=202
H=50
LeftMouseUpAction=[!CommandMeasure "MeasureSearchInput" "ExecuteBatch 1"]
[MeasureSearchInput]
Measure=Plugin
Plugin=InputText
X=4
Y=3
W=188
H=44
SolidColor=200,200,200,255
FontColor=47,47,47,255
FontSize=11
AntiAlias=1
FocusDismiss=1
UpdateDivider=-1
Command1=[!Log "$UserInput$"]
That will work as expected...
1.png
You do not have the required permissions to view the files attached to this post.