Export to GitHub

rainmeter - issue #33

Add Positioning options to !BANG command


Posted on Apr 7, 2009 by Quick Rhino

How about applying new positioning options also to !BANG command? e.g. !RainmeterMove 50% 50% [config] !RainmeterMove 100R 100B [config]

Comment #1

Posted on Apr 7, 2009 by Grumpy Hippo

Oddly, I was one of the Lightstep developers several years ago... any way, I added the support to the RainmeterWindowX and RainmeterWindowY configs, but not to the bang commands. Not sure how many people are using Rainmeter with Lightstep, but I don't have an environment to develop and test that configuration.

Comment #2

Posted on Apr 7, 2009 by Grumpy Hippo

(No comment was entered for this change.)

Comment #3

Posted on Apr 7, 2009 by Grumpy Bird

I can answer the litestep question, there are actually several folks who use it still, and Kaelri (the creator of the Enigma Config) is looking into a full package.

Apparently there has been an update to LiteStep in th elast coupleof months, and is still utilized

Comment #4

Posted on Apr 8, 2009 by Quick Rhino

Thanks for the response! Though I dont understand why it becomes a talk about LiteStep... I didn't mean to talk about LiteStep.

(brian, Thank you for fixing unsuitable owner label and also your good management :)

Comment #5

Posted on Apr 8, 2009 by Grumpy Bird

Mt bad, I will stay out of this one, apologies

Comment #6

Posted on Apr 8, 2009 by Massive Monkey

I think Sanadasan was referring to being able to set an action to move a config, either by button press or IFs.

Comment #7

Posted on Apr 8, 2009 by Grumpy Hippo

Bang commands originally came into Rainmeter from Litestep, but are used else where now.

How would we want the bang to work? Should it move the location temporarily (return to original position at the next start) or permanently (update the .ini file so the new position is maintained to the next start up)?

Comment #8

Posted on Apr 8, 2009 by Swift Rabbit

I haven't used LiteStep in several years so I'm not sure how it normally interacts with other programs using bangs.

That said, when using bangs in rainmeter I think of them as non-persistent changes. The next time the skin is loaded (startup or refresh) everything should go back to its original position in my opinion.

Comment #9

Posted on Apr 8, 2009 by Grumpy Bird

Ok, here is one. Would it be possible to set up a toggle for multiple positions? Especially in the case where folks are trying to switch between two monitors and a single monitor.

Some type of programmable profile?

Place the configs, and create profile Place Configs, and create profile

Comment #10

Posted on Apr 8, 2009 by Grumpy Bird

and possibly a default reset, that would just move all active configs back to the upper left hand corner.

I hope I am on topic here.

Comment #11

Posted on Apr 9, 2009 by Quick Rhino

Comment deleted

Comment #12

Posted on Apr 9, 2009 by Quick Rhino

Comment deleted

Comment #13

Posted on Apr 9, 2009 by Quick Rhino

Comment deleted

Comment #14

Posted on Apr 9, 2009 by Quick Rhino

Please think that this matter is not related to LiteStep at all. This idea means that a skin developer can arrange more freely in each user's screen position. For example, it could display in the just center on any user's screen like an alert box. (This sample opens a pop-up window per minute.)


[Rainmeter] BackgroundMode=1 [Minutes] Measure=TIME Format=%S IfEqualValue=59 IfEqualAction=!Execute [!RainmeterMove 400 200][!RainmeterZPos 2][!RainmeterShowMeter (alert)] ; <---Don't linebrake!! [(alert)] Meter=STRING X=1 Y=1 FontColor=FFFFFF SolidColor=00000055 FontSize=50 AntiAlias=1 Text="wClick to close" LeftMouseUpAction=!RainmeterHideMeter (alert) Hidden=1


it is possible also at the current move method like this sample, but it is difficult to arrange at the just center by absolute position definition.

How would we want the bang to work?

It is the same as the current command like "!RainmeterMove" or "!RainmeterZPos". (It means being reflected in real time at INI.) I hope the extended "!RainmeterMove" command corresponding to relative positioning. and I don't mean to hope for another new command. I'll be glad if you can understand the meaning.

Thanks

Comment #15

Posted on Jul 31, 2009 by Quick Rhino

Probably this issue seems to be able to be solved by r117.

Status: Done

Labels:
Type-Enhancement Priority-Medium