I am attempting to make a basic clock skin for rainmeter, and I am following this tutorial.
When I try to use % to display a Measure, it displays the % on the skin:
Screenshot
Here is the code:
[MeterMonthDayYear]
Meter=String
MeterStyle=TextStyle
MeasureName=MeasureMonthName
MeasureName2=MeasureDayOfMonth
MeasureName3=MeasureYear
X=204
Y=0R
FontSize=13
Text=%1 %2, %3
I double checked all of my measures, so that isn't the issue. It seems that rainmeter is just parsing the code wrong. Is there any way to fix this? Thanks!
There doesn't appear to be any obvious errors in the code you've pasted.
I think you'll either need to show more code (for example the measures used), or you can open the log (Right-click the skin, select Rainmeter -> Manage -> Open Log), then refresh your skin.
If you've made any mistakes, these will usually show up in the log as Error.
Related
Not sure if this is the correct place to post this but this issue is driving me insane....
The Issue:
I have come to use my PC after the weekend and for some reason the layout of the VBA Project stuff is completely messed up...
Usually when my VBA is set up very nicely in what I believe is the standard viewing mode IE the Project box to the left and the code to right and the intermediate window at the bottom...
For some reason now I get the following:
As you can see it is just the code...
I then click on the project explorer window and the project details appear, but as one ridiculously large page....
Then I minimise the window and alter its shape to try and get it at least look like it used to...
I can live with this to an extent although everything is floating and annoying... But now, every time I click onto a module (to view the code). It opens each module as its own seperate window!
This as you can imagine is unsustainable when working with as lot of code and having to flick between different modules
What I have Tried:
I have tried looking in different settings and I can not see anything different...
I have restarted my PC and it is still the same...
I have tired opening a different spreadsheet and still the same....
Does anyone have any suggestions? I just want it to be back to the simple layout of everything joined together etc...
When I'm dumping data from a failed macro the last thing I want is the stupid system to bleep at me.
I looked in all the options and couldn't find one.
I tried selecting and then unselecting Options>Ease of Access>Feedback Options>Provide feedback with sound (It was already unticked so I ticked and unticked it.
I tried running an On Open event with application warnings equal to false.
None of these things work. If a process stops and displays a warning message you need to click it doesn't need a sound to accompany it.
I know I could switch the sound off but what if I want to listen to music or a podcast?
it's extremely irritating and I'm dumbfounded that it's easier to jump out of a window than disable a totally un-necessary source of irritation.
So you've tagged this question Excel and VBA, but Options > Ease of Access > Feedback Options > Provide feedback with sound does not exist in the Visual Basic Editor (VBE). Not sure where you're getting that from.
Anyway, the easiest way to achieve this is hitting Alt+F11 and then going to Tools > Options in the in the VBE and then unticking "Auto Syntax Check".
Faulty code will still be marked in red (or whatever color you've chosen on the Editor Format tab), but the pop-up error message will not be shown and the annoying system beep will no longer be played.
It should be noted that this will NOT prevent run-time error beeps, only syntax error beeps during coding in the VBE. I suppose you could write a Windows API call to the winmm.dll file which plays system sounds, if you also want to get rid of the system sound accompanying run-time errors.
I just got Dreamweaver CC and the color coding is not working what-so-ever. I've already done the following:
I tried to put checkmark by "Syntax Coloring"under the View menu, but it will not let me check it. It's not grayed out; it just won't let me check it.
I downloaded a new Color xml file,and placed it in the Configurations folder.
I tried changing the colors around in a file in the Preference menu, but it won't apply the colors.
I deleted the Configurations folder so it will reset to default, but nothing.
You guys are my last resort. If I can't get it to work I will have to re-install the entire program. Any suggestions?
Honestly, your best bet after going through all of those steps would be to, unfortunately, utilize your final option of re-installing Dreamweaver CC. Sorry if this isn't the answer you were expecting but that's what I would do at this point. Good luck!
I figured it out; and, I'm posting the solution to my own problem so readers won't endure as much suffering as I did trying to find the solution to this problem. This little bitty tinny issue made my life miserable for several days. Anyway, look below for the answer:
I had my HP Envy laptop running Win 8.1 color displayed set to high contrast. Big mistake! I changed it back to display colors and my problem was solved.
I am having a strange Excel 2007 issue, and I am not quite sure how to explain this. So bear with me please....
I have created a few right click buttons to call various backend VBA functions that I have written. They were working fine earlier today, and now for some reason, a button is appearing that is not from the code in my worksheet. When you click it, it is attempting to open another worksheet and execute code from it. The two files are not in the same directory nor are they named anything similar. I deleted the file that the button is trying to execute from and now it just simply gives me an error 400.
So, I couldn’t figure that out, and have since deleted every single scrap of code in the backend of this file, and the button still appears. Any ideas what could be causing this? It seems like maybe its mixing files up or saving a copy somewhere in a temp directory and trying to access that instead of the actual code that is written in the VBA. Is there a cache I need to clear out or something?
I know I didn’t exactly do a great job describing this, so I will be more than happy to provide any and all other details that you may need. Just let me know what is going on.
EDIT #1 -- New Information ==
I can even open a new, completely blank excel file and the right click button is still there.
EDIT #2 -- Tried Diagnostics ==
I just tried running the Excel diagnostics and it found no problems. It is strange, it is like this macro has somehow became global or stored in some type of cache or something.
I hope I'm understanding your issue correctly.
If you know what right-click (context) menus the button is appearing in you should be able to fix them with a Reset command. For example if it's appearing in the Cell context menu, you could try this in the VBE's Immediate window:
Application.Commandbars("Cell").Reset
This will reset the entire menu to its default state.
Also, you might be interested in a tool I wrote, MenuRighter, that allows you to tweak your right-click menus. It also has a setting to show you the Caption and ID of any context menu.
I'm using the Ribbon control located on CodePlex, and following the tutorial located here . Once I add the reference, and the proper code in the designer I get this error when I try to view the form:
Exception of type 'System.ComponentModel.Design.ExceptionCollection' was thrown
And I cant figure out what I'm doing wrong. Anyone worked with this control and know how to resolve this issue?
Interesting; I just ran into this same issue with one of my own forms; which is how I found your relevant and recent question.
Here's how I solved it:
Open two instances of Visual Studio. Open the same project in both.
In one instance, goto Debug->Exceptions and enable all the 'Thrown' options to stop at first chance exceptions. This will stop the debugger when the exception is generated.
In the same instance, select Debug->Attach to Process, select devenv.exe.
In the other instance, open the form to cause the exception
With any luck the first instance should stop somewhere that yields a more relevant exception.
In my case it turned out to be something that I should have conditioned with:
if (!DesignMode)
{
// Do something that should only happen at runtime
}
Don't forget turn turn off all those 'Thrown' options later.
A workaround for me was:
Right-click on the form and 'View Code'
Keep the code loaded in the editor and then attempt to view the designer again.
This feels very glitchy and I cannot confirm whether it's a problem with my code (as I'm working on an entirely new codebase) or whether it's a VS2012 bug. If I find out, I will report back.
Since the solution outlined by pilotcam didn't work for me, I took a different approach:
Make a SVN commit for the file.
Open the “*.designer.cs” file of the form that shows the error in source view.
Remove larger blocks of form element declarations.
Fix all compilation errors with ReSharper (i.e. ensure that nothing is red anymore on the side-indicator).
Save the file. No need to compile.
Open the Windows Forms Designer of the form.
If the error still shows up, do a SVN revert to go back to the initial state.
Repeat steps 2 to 7 until the error does not show up anymore.
Now you’ve encircled the erroneous child control that causes the error.
Repeat steps 2 to 7 with a smaller amount of controls you remove, until you have only one control left.
In my case it was a user control inside a group control inside a tab control, so I first identified the tab control, then the group control and then the user control.
You could isolate the user control inside a new form to further investigate. In my case it was rather easy; I put checks for design mode around most of the functions inside my control to ensure the code only gets executed if the control is not in design mode.
This fixed my error.
I had the same issue and none of the above answers solved the problem.
At the end, emptying the "bin" folder and rebuild has worked for me.
Let me add two more cases when such exception can happen, along with when control tries to do something that is not allowed under design mode:
When it's impossible to compile the user control.
When designer code contains multiple similar (or identical) lines with initialization of same controls or properties, this can easily happen on merge.
All that cases produce same extremely meaningful error message, and in this particular two debugging of Visual Studio won't help, so I just ended up with bisecting my designer code.
[ReadOnly(true)]
[Browsable(false)]
Above all properties worked for me