I really want to use this mClock skin on my mdpi optimus V, ,but it comes out looking like this:
No amount of resizing or choosing different widget sizes helps, so I know that the xml needs to be edited. If it was just the font size, I could probably handle it, but I have a feeling that with font size changes, spacing issues will arise, and well, my xml-fu is weak to say the least
If someone could edit it for me, I would much appreciate it.
Thank you in advance
(also having the same issue with the typoclock skin, if anyone is willing)
I know, but ill either get snarked to death or told to do it myself. That is if my all important post count is high enough to even ask. I thought I'd ask the nice(er) people here first. Figured someone here would know how, but I guess not.
I actually just read that thread today but if I post my request there, odds are it will just get moved to the mclock thread. Anywho, I posted it here specifically in hopes to avoid having to go to xda. :P
I really want to use this mClock skin on my mdpi optimus V, ,but it comes out looking like this:
No amount of resizing or choosing different widget sizes helps, so I know that the xml needs to be edited. If it was just the font size, I could probably handle it, but I have a feeling that with font size changes, spacing issues will arise, and well, my xml-fu is weak to say the least
If someone could edit it for me, I would much appreciate it.
Thank you in advance
(also having the same issue with the typoclock skin, if anyone is willing)
IF you wish, I would love to help you. I have coded a ton of skins for the mclock widget. I run a design studio and we modify all types of skins for the mclock. Our studios FluxboxMedia - 510Studios , is known for Android modifications and tutorials. Email it to geektekneek@gmail.com
We will take care of anything you wish or need on that skin.
Check out our Youtube channel for tutorials and such. We will be posting a XML Editing tutorial soon on this.
Just from the screen grab you have there it almost looks like you don't have much more than either 4 columns in your homescreen or 3. You will need at minimum 5 to show this accurately. I would check that also before any shrinking or XML is needed. We will help anyway we can, but that was the first thing that our design team noticed by the pics.
Hope this helps also. We found the XML in the post, so we are looking at it now.
Thanks.
FBM Team
IF you can, open the file you have which is your XML or open a new text document and copy this in and try it. We have updated the sizes and alignments :
Your Welcome! Here try this, might fix the time issue. It's a matter of adjusting the margin along w/ the Font size. From 80 or so to like 30-40 and the smaller ones from 40 to like 20 or less.
6 Columns good.
I can help you, I also use this clock skin and know the developer. You have to have your homescreen set to a grid of 5x5. This particular clock skin called Offset Clock uses the 5x1 widget only. That way it will show properly.
well its close, but still cuts off the last minute digit. reset my homescreen to 5 column grid, chose 5x1 widget. top one I stretched down to make it bigger, bottom one is exactly how it looks when I apply it, nothing moved or stretched (its tiny, that's why I stretched the top one) and both cut off the 9 in 10h 59 :/
well its close, but still cuts off the last minute digit. reset my homescreen to 5 column grid, chose 5x1 widget. top one I stretched down to make it bigger, bottom one is exactly how it looks when I apply it, nothing moved or stretched (its tiny, that's why I stretched the top one) and both cut off the 9 in 10h 59 :/
I'm not sure which .xml file you are using above, but why not start fresh with the original files. You can download the .zip of all the colors.
whoa, I guess it is just the resolution of your screen, I am on the Galaxy SII Epic. Can I suggest that you play with it and maybe try the 4x1 widget size. Once you get it looking right, then you'll know what size you need to use. The developer tested it on a Galaxy SII as well, but I know others are using it on a Captivate and a Fascinate and it works fine.
And this is why I jumped in here and custom edited the XML for her. YOU both didn't get it from the first time that she posted it. That she was having issues on default. I will customize the xml again and see if that works on the 8 x 6 or however she has it. I know at least w/ my xml on that it was working partially all but the last parts.
Thanks for the feedback.
Here try this, the problem that you are running into when you are having the digits and their size at the location is that the margin is too far offset. So i adjusted this to allow the text to float more to the center. Let me know how this works on the 8x6 or however you had it. :
By decreasing the STACK Horizontal alignment from the 85 or whatever it is by default, you allow the blocks of text to float back to center as outlined in the first part of the XML or as the application calls by default. So by pushing the size down to like 60 you are decreasing the space between the day text to the hour text and allowing it to be more on the screen.
Hope this works.
*fyi, just cause you know the developer only shows that you know someone, it does not ever prove that you understand code , or the language of how the SDK or apps are coded and configured. I can say that I know Bill Gates, but does that automatically make me able to know every bit of the 300000+ lines of code in .net 2008 and C++ call to stacks which make up the OS of Windows 7, no. Not at all, so before you go pirating a thread and Name tossing, think about it, cause it does not get you any higher up the chain*
The Following User Says Thank You to fluxbox For This Useful Post:
whoa, I guess it is just the resolution of your screen, I am on the Galaxy SII Epic. Can I suggest that you play with it and maybe try the 4x1 widget size. Once you get it looking right, then you'll know what size you need to use. The developer tested it on a Galaxy SII as well, but I know others are using it on a Captivate and a Fascinate and it works fine.
Yeah I'm using an optimus v. Mdpi screen. I'm guessing the ones you mentioned are hdpi. Hence the request. I did think to play around with widget sizes and resizing and whatnot before I made the request
EDIT: That last one worked perfectly! Thank you so much!!
Last edited by sadielynn; November 19th, 2011 at 01:12 PM.
The Following User Says Thank You to sadielynn For This Useful Post:
You are most welcome and I do believe you are correct that in most cases the widgets are for the HDPI and not the MDPI. Our studio doesn't have many of those proprietary devices on set. We have alot of the larger screen devices. No bother tho, we all in our office have expertise at one thing or another in the Android Community so it's our pleasure to give back and help. If you ever need anything else adjusted, let us know.
Thanks again!
Nice screen btw.
Sincerely,
510Studios and FluxboxMedia Team
Quote:
Originally Posted by sadielynn
Yeah I'm using an optimus v. Mdpi screen. I'm guessing the ones you mentioned are hdpi. Hence the request. I did think to play around with widget sizes and resizing and whatnot before I made the request
EDIT: That last one worked perfectly! Thank you so much!!
*fyi, just cause you know the developer only shows that you know someone, it does not ever prove that you understand code , or the language of how the SDK or apps are coded and configured. I can say that I know Bill Gates, but does that automatically make me able to know every bit of the 300000+ lines of code in .net 2008 and C++ call to stacks which make up the OS of Windows 7, no. Not at all, so before you go pirating a thread and Name tossing, think about it, cause it does not get you any higher up the chain*
What, pirating a thread like you have, where you alter an xml coding developed by someone else without obtaining their permission, just to show off your own skills. Right. End of discussion.
Need xml/mclock help please
End of discussion.
