TextBox with Header - Windows Phone 7 General

This is exactly what I like to have:
http://msdn.microsoft.com/en-us/library/hh202916(v=vs.92).aspx
Since there exists no standard control I have written one by myself but I didn't get DataBinding to work (even when using correct implementation of DependencyProperty)
Got 25 votes for:
http://wpdev.uservoice.com/forums/1...474043-add-header-property-to-textbox-control

Simple
I think for that screenshot on the MSDN page you give they did what I also did without thinking twice in my own apps: Place TextBlock controls immediately before the TextBox controls.
Indeed, I found the approach of some controls with built-in header text property annoying because they waste a line of space even if you don't need a text.
And where would you stop with your new header property because sometimes you need text in front of a text box, but sometimes below, or in front and in the back at the same time, etc. (Yes, that does not happen with trivial, 3 textbox screens, but drive up the number of features in your program and it will probably happen.)

Don't agree. A HeaderMode enum should do the trick. I don't want do reinvent the wheel each time I need a simple TextBox After a year implementing WP apps I still see advantages of a TextBoxWithHeader control.
Sent from my RM-821_eu_euro2_530 using XDA Windows Phone App

Related

start up - notes

as most of you know personal info contains also a note and you can set up that whenever you turn on your device this will show up
but to access this field you have to go quite far (toooo many clicks away)
my question is - is there any simple way to access and edit this note? can you make shorcut to standard HTC Home or assing it to any button when pressed longer?
thx
I cannot have my identification info and/or notes displayed on my home screen with TF3D. How do you do that?
I'd love to have some program / tweak to really edit the TF3D. Been waiting for more than a year now, Clock is too big, I can see too few appointsments and I'd like to see notes. Just like you had on that old Nokia.
EDIT: Nevermind, it functions as a sort of screensaver I found out now. Haven't found a quicker way to access the notes though.
EDIT2: The notes screen seems to be cut off after 6 lines. Any way to have it fill the full screen? Now I can only add 5 lines of notes (sixth line is already displayed with the bottom mm cut off) and I have about 10 lines white at the bottom.
I can see 6 lines, that is really strange, based on the space of the whole display and its capabilites ..
never the less I could use some shortcut ...

Using WM6.5.x Control styles in own (.NET) programs?

Hello,
since WM6.5.3 the standard Controls like Buttons, Comboboxes, TabControls, Checkboxes etc. have a new Style with gradient Backgrounds and sometimes rounded edges.
If you develop programs with the .NET CF you will get the boring old style. Is there any way to enable the new style for .NET applications?
The only thing I found was this "hack" for the TabControl:
mobileworld.appamundi.com/blogs/peterfoot/archive/2009/09/17/windows-mobile-6-5-tab-control.aspx
(sorry, seems that I'm not allowed to post outside links)
I searched a lot for this but even the documentation from Microsoft gives no hint how to do this.
There is also a new control in many system control panels which replaces the TabControl (the navigation thing at top of the form for example in sounds and notification settings). Is there any chance to use this control in my own programs?
It is really annoying that Microsoft has developed a new themeable style for their controls and nobody can use it
Thanks a lot
Markus
You can but it requires overriding the controls paint events and imo is not worth the hassle. If you want fancy looking controls then you would be better off with 3rd party controls. There's several options out there and some are free. Read about some at http://forum.xda-developers.com/showthread.php?t=616838
If you want to work with the native controls and spruce them up a bit check out http://code.msdn.microsoft.com/uiframework for some guidance.
Ren13B said:
You can but it requires overriding the controls paint events and imo is not orth the hassle.
Click to expand...
Click to collapse
thanks for your answer but I don't want to create custom controls or use some 3rd party controls. I want to use the standard controls but with the WM6.5.x style.
Microsoft is really stupid. They were on a good way with 6.5.x. The user interface of the standard apps is mostly consistent and finger friendly. But they forget 3rd party developers now completely. I want to be able to create apps with the system look and feel but it seems that it is not possible. So my own applications have always an inconsistent look when I use standard controls. I always get the old style but when I open a messagebox then I get buttons in the new style.
Microsoft, this is really crap!
You'll have to wait for Windows Phone 7 if you want perfect consistency. Microsoft isn't going to update the controls for 6.5.
Hey there!
Today I did some research into controls, and I found out how to enable 6.5.3 style for buttons and checkboxes. You have to:
edit2: for dialogs - open .rc file in a text editor, and find your dialog, then after a line beggining with STYLE add a line with following contents:
Code:
EXSTYLE 0x1800000
Compile it and run. You should get 6.5.3 look and feel on existing controls without changing them!
Or if you want to create controls in runtime (works good for buttons, checkboxes/radio buttons look ugly):
1) call SHInitExtraControls()
2) when creating a button/checkbox use class TTBUTTON and make sure its style is combined with 0x8000
3) Use 'em like normal buttons.
Now it's time for listboxes & others...
edit2: To mimic 6.5.3 listbox behavior you have to set item height to 64 (or 32 for (W)QVGA), for example in this way:
Code:
SendDlgItemMessage(hwndDlg, IDC_COMBO1, CB_SETITEMHEIGHT, -1, 64);
SendDlgItemMessage(hwndDlg, IDC_COMBO1, CB_SETITEMHEIGHT, 0, 64);
To expand list views, use a empty image list with a proper image height (64 or 32), for example:
Code:
HIMAGELIST il;
il = ImageList_Create(1, 64, ILC_COLOR, 0, 1);
SendDlgItemMessage(hwnd, IDC_LIST1, LVM_SETIMAGELIST, LVSIL_SMALL, (LPARAM) il);
edit: Oops, forgot you want it in .NET. Quick investigation lead me to a sad fact: .NET controls have the wrong window class. But if .NET dialogs are stored in resources there is hope. So I would be grateful if someone post here a compiled .NET application which would show a dialog with a button linked to some simple action. I might try to modify it for 6.5.3 style.

[24/08/2010] first development project 4 on 1 row

intro: I'm a bachelor student who has a little knowledge of programming.
For the first time i try to make a simple game that i already wrote in java work in vb.
I'm planning to make this a full working game that I can place on the market place for free.
I already have the idea how to make the AI to play 1 vs PPC
I wrote it for a WVGA screen but its completely dynamic so it should work on other screen sizes.
Only when you change the orientation the text will not be visible (need to think where i'm gonna place it)
pls feel free to give input on the project.
I uploaded the whole vb net directory so its open for everybody
(Im still a bit strugling with a cab file that has links in it
if you instal it, it should be visible in the programfiles dir)
--edited 24/08
-thanks to Gaz25 the refresh problem is soved
-the 4 on a row detection algorithm is completed
Hi, I had a look at your code and fixed your flicker problem.
Basically, when you do you own drawing on a control like a panel you need to take control of painting the background as when a control is redrawn it paints the background first and then anything else on top like text, images etc...
The best thing to do is create a custom control. Then you can override the OnBackgroundPaint event and say do nothing.
Then override the OnPaint event and here is another trick.
In the OnPaint event, create a bitmap. This will be the 'backbuffer' which you will do all your drawing on. Then when you have done all your drawing on the backbuffer, you draw the backbuffer to the screen.
I have included your solution with my modification which I hope make more sense .
If you need more explanation then let me know and I will go into more detail.
Gaz25 said:
Hi, I had a look at your code and fixed your flicker problem.
Basically, when you do you own drawing on a control like a panel you need to take control of painting the background as when a control is redrawn it paints the background first and then anything else on top like text, images etc...
The best thing to do is create a custom control. Then you can override the OnBackgroundPaint event and say do nothing.
Then override the OnPaint event and here is another trick.
In the OnPaint event, create a bitmap. This will be the 'backbuffer' which you will do all your drawing on. Then when you have done all your drawing on the backbuffer, you draw the backbuffer to the screen.
I have included your solution with my modification which I hope make more sense .
If you need more explanation then let me know and I will go into more detail.
Click to expand...
Click to collapse
i will look at it monday when i'm back from a festival
thanks in advance.
sended from x1
Thank you very mutch,
i just tested it and it works perfect.
I will try to make it better in the following weeks.
Only one thing that you changed in my code that wasn't correct "speler = 0" (on load, needs to be 1 or 2) (speler = player)
I also found an error in my own algortim for the 4 on a row detection
"teller1 = teller2 = 0" ( gave me a -1 on teller1)

What's wrong with ICS and the Galaxy Nexus

First off; I love Android. I think that Ice Cream Sandwich has led to a greater harmonisation of the Android operating system and adds a bit of polish to something functional. Google's apps are starting to feel like they belong together, rather than giving a sense that they're being produced by different teams who have little contact.
However, I'm no fanboy. I don't buy a product and deny that it has flaws just because a certain company produced it *ahem *. So here it is; one humble man's opinion on what's wrong with Ice cream Sandwich.
1. Blue theme.... really? There's a reason that designers avoid blue-on-black. It offers poor contrast, and looks cheap; much like the Geocities sites of the 90s. The blue taskbar and app icons used in ICS just don't go with... well... anything. It's all well and good being able to customise your home screen, but when anything except a blue background clashes it's all a little redundant.
2. The stock icons themselves are disgusting. We all knew this from the leaked screenshots, which forums were praying were fake. Mostly, they just don't look like they belong to the same set. There's no consistency. Half are blue, half are not. Some are three dimensional, and some are traditional, flat icons. Some are different sizes. They just don't work. They look cheap, childish and don't match the 'magazine' style of the UI overhaul. It's like someone realised at the last minute that they'd forgotten to redesign icons, so just did a Google Image search and used the first of each that they found.
3. Google Plus pages won't open in the Android Browser. This one is just plain embarrassing. Google's flagship device can't view Google's new hub outside of the restrictive app? The browser just panics and shuts down with no option to report it. Did no-one test this?
4. Google Talk isn't in the sharing options. That's right, click on the share icon within an app and it'll show you every way of sharing except Google Talk. Following the above, it seems like Google is boycotting their own services.
5. Speech to text for UK language setting is insane. After a few words, it seemingly switches to using your contacts directory as a dictionary, rather than real words. You end up with a full sentence made entirely of surnames and forenames. I cannot believe that no-one tested this.
6. Removing the search key doesn't just remove the ability to search from some apps; it means that you can no longer assign functions to long press, or use voice command from any app. You have to return to the home screen each time. This is a huge step backwards.
7. Similarly, this has led to a non-removable search box on the home screen. Not only does it take up space, but the white icon doesn't work on a light background. The customisability of Android has just been taken down another notch. Sure, you can use a 3rd party launcher, but with no search button, you need the box there for searches.
8. A minor point, but Android can't seem to decide if going for a futuristic hologram look, or the Windows Phone 7 style magazine layout. It's like Mathias Duarte turned up, and they said “Make our OS beautiful... but it still has to look like ugly old Honeycomb (TRON)." All in, it just feels a bit cheap and confused.
9. The soft keys which Google has opted for in ICS are not well positioned. The home key is far too close to the space bar, which is infuriating when typing.
10. The action bar is horrific to use. It means that the menu and search keys jump around the screen. So you're in the Facebook app and want to see the menu. Where is it? Well it's not where it used to be and there's no action bar. Oh wait, three dots have appeared in the soft-key bar. Ugly and inconsistent, but OK.
Switch to messaging. Where the heck is it? Ah it's in the top right now! The little scamp.
Now you're in Gmail. Where is the menace? I know you're here somewhere... Ah, there! In the action bar in the bottom right. Android Market: back up top! There is just no consistency and it makes everything feel disjointed and unpredictable.
The action bar essentially negates the large screen on the Galaxy Nexus. The row of soft keys, plus the action bar actually leads to a lower proportion of screen space for the app than on previous versions of Android.
11. Cut, Copy & Paste: What the hell were they thinking?! This doesn't just jump around based on app, but depending on which page of an app you're in. And even then, the buttons are different every time.
Take Gmail for example. Copying text from the body of an email: a menu appears in place of the action bar at the bottom. However, in the 'compose' screen this menu appears at the top, but with different icons. Another 'paste' button (but not using the paste icon) also appears above the selected text, but no cut or copy buttons. If you try and make a selection from a link, a long press summons a pop-up dialogue where paste is an option. That is four ways of pasting, just within the Gmail app.
Not to mention, that they've opted for icons with no words. Unless you're accustomed to using old Windows machines, this may as well be code. It's like it's intentionally trying to confuse you.
12. Relationships with app vendors must be non-existent. If I was releasing an update to a platform which relies upon people being able to install apps, I'd make sure that the most common apps work on the new platform before release. This could involve providing phones and assistance to the big names. As it stands, neither Facebook nor Whatsapp (two of the top 5 most downloaded apps) work. Both of these are communications related. I feel cut off from the world. I'm sure this could have been sorted before release. Swype is another big name that doesn't support the screen resolution.
Google launched the Galaxy Nexus weeks ago. Facebook was initially unusable due to the absence of a menu button. The app was updated today to a version akin to the iPhone. However, the drag-to- refresh animations don't work as they should, and the damn thing will alert you of 'new messages' every 30 minutes if you have any unread, regardless of whether or not they are new. Atop this, Facebook will still not sync with official Google devices as Facebook does not properly use Google's contact API. Rather than being stubborn, Google should be helping Facebook, or seconding engineers, as they know full well that the majority of their users will require his service.
I appreciate that a lot of this is out of Google's hands, but this is just a warning to early-adopters – be prepared to lose the services you use most.
13. The browser is still useless with forms. Try entering text in a field. It'll type past the edge of your viewport and you can't scroll to the cursor. The viewport should follow the cursor. You can't zoom in and out because you can't get 'hold' of the web page due to the full-screen text entry field.
14. Horizontal lines everywhere. Did I mention that text fields are now horizontal lines? Text boxes are indistinguishable from divides and text doesn't sit on the lines so you never know where one ends and the other starts.
As I said, all in, it is an improvement. However, there is a heck of a lot of room for improvement. There is still a feeling that things aren't really designed, or connected; just a bit haphazard. I'm just hoping Cyanogen pulls something wonderful. For the standard consumer, the experience aspect is still playing catchup with Windows Phone and iOS.
I agree with most of what you are saying... nothing makes me angrier than trying to use google search on android's mobile browser, and not being able to add additional words onto the end of my search string because I can't Freaking scroll the text over to enter it in. (I do think this is a webpage issue possible though, because it happens on iphone as well)
I think they should have gotten rid of the flip button (task switcher button) and have that be the settings button, then just have the HOME button be a long press for task switching.... simple, effective, makes sense.. consistent. I guess having settings in the app allows developers to have more control, but I think consistency would be better.
mike freegan said:
First off; I love Android. I think that Ice Cream Sandwich has led to a greater harmonisation of the Android operating system and adds a bit of polish to something functional. Google's apps are starting to feel like they belong together, rather than giving a sense that they're being produced by different teams who have little contact.
However, I'm no fanboy. I don't buy a product and deny that it has flaws just because a certain company produced it *ahem *. So here it is; one humble man's opinion on what's wrong with Ice cream Sandwich.
1. Blue theme.... really? There's a reason that designers avoid blue-on-black. It offers poor contrast, and looks cheap; much like the Geocities sites of the 90s. The blue taskbar and app icons used in ICS just don't go with... well... anything. It's all well and good being able to customise your home screen, but when anything except a blue background clashes it's all a little redundant.
2. The stock icons themselves are disgusting. We all knew this from the leaked screenshots, which forums were praying were fake. Mostly, they just don't look like they belong to the same set. There's no consistency. Half are blue, half are not. Some are three dimensional, and some are traditional, flat icons. Some are different sizes. They just don't work. They look cheap, childish and don't match the 'magazine' style of the UI overhaul. It's like someone realised at the last minute that they'd forgotten to redesign icons, so just did a Google Image search and used the first of each that they found.
3. Google Plus pages won't open in the Android Browser. This one is just plain embarrassing. Google's flagship device can't view Google's new hub outside of the restrictive app? The browser just panics and shuts down with no option to report it. Did no-one test this?
4. Google Talk isn't in the sharing options. That's right, click on the share icon within an app and it'll show you every way of sharing except Google Talk. Following the above, it seems like Google is boycotting their own services.
5. Speech to text for UK language setting is insane. After a few words, it seemingly switches to using your contacts directory as a dictionary, rather than real words. You end up with a full sentence made entirely of surnames and forenames. I cannot believe that no-one tested this.
6. Removing the search key doesn't just remove the ability to search from some apps; it means that you can no longer assign functions to long press, or use voice command from any app. You have to return to the home screen each time. This is a huge step backwards.
7. Similarly, this has led to a non-removable search box on the home screen. Not only does it take up space, but the white icon doesn't work on a light background. The customisability of Android has just been taken down another notch. Sure, you can use a 3rd party launcher, but with no search button, you need the box there for searches.
8. A minor point, but Android can't seem to decide if going for a futuristic hologram look, or the Windows Phone 7 style magazine layout. It's like Mathias Duarte turned up, and they said “Make our OS beautiful... but it still has to look like ugly old Honeycomb (TRON)." All in, it just feels a bit cheap and confused.
9. The soft keys which Google has opted for in ICS are not well positioned. The home key is far too close to the space bar, which is infuriating when typing.
10. The action bar is horrific to use. It means that the menu and search keys jump around the screen. So you're in the Facebook app and want to see the menu. Where is it? Well it's not where it used to be and there's no action bar. Oh wait, three dots have appeared in the soft-key bar. Ugly and inconsistent, but OK.
Switch to messaging. Where the heck is it? Ah it's in the top right now! The little scamp.
Now you're in Gmail. Where is the menace? I know you're here somewhere... Ah, there! In the action bar in the bottom right. Android Market: back up top! There is just no consistency and it makes everything feel disjointed and unpredictable.
The action bar essentially negates the large screen on the Galaxy Nexus. The row of soft keys, plus the action bar actually leads to a lower proportion of screen space for the app than on previous versions of Android.
11. Cut, Copy & Paste: What the hell were they thinking?! This doesn't just jump around based on app, but depending on which page of an app you're in. And even then, the buttons are different every time.
Take Gmail for example. Copying text from the body of an email: a menu appears in place of the action bar at the bottom. However, in the 'compose' screen this menu appears at the top, but with different icons. Another 'paste' button (but not using the paste icon) also appears above the selected text, but no cut or copy buttons. If you try and make a selection from a link, a long press summons a pop-up dialogue where paste is an option. That is four ways of pasting, just within the Gmail app.
Not to mention, that they've opted for icons with no words. Unless you're accustomed to using old Windows machines, this may as well be code. It's like it's intentionally trying to confuse you.
12. Relationships with app vendors must be non-existent. If I was releasing an update to a platform which relies upon people being able to install apps, I'd make sure that the most common apps work on the new platform before release. This could involve providing phones and assistance to the big names. As it stands, neither Facebook nor Whatsapp (two of the top 5 most downloaded apps) work. Both of these are communications related. I feel cut off from the world. I'm sure this could have been sorted before release. Swype is another big name that doesn't support the screen resolution.
Google launched the Galaxy Nexus weeks ago. Facebook was initially unusable due to the absence of a menu button. The app was updated today to a version akin to the iPhone. However, the drag-to- refresh animations don't work as they should, and the damn thing will alert you of 'new messages' every 30 minutes if you have any unread, regardless of whether or not they are new. Atop this, Facebook will still not sync with official Google devices as Facebook does not properly use Google's contact API. Rather than being stubborn, Google should be helping Facebook, or seconding engineers, as they know full well that the majority of their users will require his service.
I appreciate that a lot of this is out of Google's hands, but this is just a warning to early-adopters – be prepared to lose the services you use most.
13. The browser is still useless with forms. Try entering text in a field. It'll type past the edge of your viewport and you can't scroll to the cursor. The viewport should follow the cursor. You can't zoom in and out because you can't get 'hold' of the web page due to the full-screen text entry field.
14. Horizontal lines everywhere. Did I mention that text fields are now horizontal lines? Text boxes are indistinguishable from divides and text doesn't sit on the lines so you never know where one ends and the other starts.
As I said, all in, it is an improvement. However, there is a heck of a lot of room for improvement. There is still a feeling that things aren't really designed, or connected; just a bit haphazard. I'm just hoping Cyanogen pulls something wonderful. For the standard consumer, the experience aspect is still playing catchup with Windows Phone and iOS.
Click to expand...
Click to collapse
yawns, i respect your opinion. But i can list 15 things wrong with IOS5 as well. Overall ICS and android has matured over the few years android has existed. No product software/hardware is perfect. Most of the issues can be corrected with customization. Like i said i respect your complaints and opinions, but i just feel they are picky...Comparing the OS from my G1 to what android is now, i LOVE IT
Thanks for typing this up. While I still plan on buying it, I like to get a well-rounded opinion about the device and software. I have to agree with #12. Launching this device exclusively on one carrier and then delaying it is very embarrasing. I know, the better developers will have a Verizon account or buy the phone unlocked from an international dealer, but still not good. It makes it more difficult for app developers to work their apps for ICS.
I had to laugh at Eric Schmidt's thought that ICS will be #1 for development in 6 months. ICS wont be off exclusivity or on any other devices for at least 3 months.
First of all, the theme Android has used for Honeycomb and ICS - holographic, blue themes, etc. - is awesome. Everybody has their own opinion but for me it's no turn off.
As far as action button placement, Google's central idea on that is leave it to the developer to say where it goes - in the top bar? Bottom ribbon action bar? Wherever is more appropriate for the app design. Matias himself said he's pushing Android to a more unified UI style without straight-jacketing it (ala iOS).
As for apps being compatible with new releases, it's up to the developers to keep that up. Google is not responsible for if Swype or Facebook doesn't update their app before a new release.
And for saying Google should help Facebook, why should they? You realize Google has their own social network, don't you? It sounds like you do know that in the past Google has let Facebook basically hack their way into your contacts list separate from the Contacts API, but later blacklisted that because it didn't conform to their data exportability policy and API. "the majority of their users will require his [sic] service." Since the 2.3 update that cut out Facebook's hackish ways, customers who want Facebook integration in their Android phones should get something non-Nexus. That's why Google is advertising the deep integration with G+, not social media in general.
mike freegan said:
First off; I love Android.
- cut -
Click to expand...
Click to collapse
Couldn't agree more. This could easily become the best Android phone I've bought (and I had them all), but at the same time it's the first one (and only one) I cannot stand because of the too many hiccups and bugs it has. Can you believe that I haven't put my main SIMcard in it yet? I keep playing with it at home, trying new roms and kernels, but when it comes to using it as my main phone... we're a long way from it!
- The Stock browser is not that good (have you tried to write something in a forum and then move the cursor back in the text to change a word? Good luck with that!!) and Dolphin Browser is not yet supported.
- As we know, Flash doesn't work yet (this is just hilarious).
- The stock Keyboard in the browser doesn't correct your mispelled words, and Smart Keyboard Pro doesn't work all the times.
- speakers are too quite, I have found a workaround using Volume + (but beware! The version available in the market is not working).
- if you try any animated wallpaper, UI will slow down painfully.
In the end as much as I love its gorgeous screen and huge potential, as things are now, I find it one of the most detestable phones out there.
Great job, Samsung/Google!
Nice write up....but so many of your complaints are just because you don't like them. Really your complaining about the color.... I'm sorry so much bothers you because honestly ICS makes Android and the Galaxy Nexus a great phone! Windows phone is a far cry from being compared to Android and IOS.
I'm all for putting out there the faults of devices but if you say I like Android -cut- I hate everything about it bla bla bla....um... how can you like it if you think another brand or device works better?? Wouldn't that mean you like _____ << insert favorite OS here??
Danny80y said:
Windows phone is a far cry from being compared to Android and IOS.
Click to expand...
Click to collapse
But on my Lumia 800 I can write effortlessly on this and every other forum, and things just work well!
I agree, colour is generally subjective. But what they've gone for is almost universally accepted as a poor choice by designers.
And to the dude above: I know very well that I can patch around a lot of these issues. I mentioned that in the article. However, most users buy this phone, don't root and don't change much.
ICS is good. IT could have been great.
And saying Google shouldn't be concerned that third party apps don't work is incredibly ignorant.
I was just using Whatapp two days ago and it was working fine. Is there something specific you were having problems with?
Three words. Point Zero one.
jrl022 said:
I was just using Whatapp two days ago and it was working fine. Is there something specific you were having problems with?
Click to expand...
Click to collapse
Mine FCs on startup. I think having group chats may kill it. I've read this in a few places.
All I see is waaah waah wahhh
I have to respectfully disagree with most of your observations.
I love almost everything about the redesign. I don't miss the search button at all. I love the color scheme, and don't really care about app incompatibilities because well, it's a Nexus device. It's a brand new OS version and really made for early adopters. Developers will work out the kinks and you'll see more ICS support for common apps in the next week or two, I'd guess.
I do agree with you about the inconsistent action bar. Google should put it in one place for all their core apps. 3rd party apps, you can't dictate, though. I don't mind the slight difference in look in some apps, though. I love the new People app and the way it's set up. But I don't think it fits in everywhere, so I'm glad they didn't force it in all over the place and try to look like WP7.
I can't comment on the UK speech settings, as I'm in the US and not using it. Really lame if it doesn't work, though. I also don't really mind the new text box look. It was a little confusing when I first saw it, but they're not that hard to recognize after you get used to it. I have mixed feelings about the permanent search box. I like it because it doesn't take a ton of space - especially with the 720p display. But I wish there was more customization.
All that said, I think the positives hugely outweigh the negatives. Most of what you posted is a little nitpicking. I don't blame you complaining about things not working as they should, but beyond that, I think the OS has come a very long way and looks amazing all around. Google has already said this is just the beginning of Android's design changes to make it more accessible and fun to use.
I can't wait to see Cyanogenmod's finished launcher. I know they made the search box removable, but we'll see. I do still love the stock launcher, too.
The ultimate question is:
Would you use another OS? I sure as hell would not! ICS is the best thing out there right now by far.
The ultimate question is:
Would you use another OS? I sure as hell would not! ICS is the best thing out there right now by far.
Click to expand...
Click to collapse
agreed. i can't go back to either iOS or GB after using ics for the last 2
weeks
Sent from my Galaxy Nexus using Tapatalk
To add the injuries, here are some things that are bad in ICS:
1. Contact photo is still low resolution after synced with GMAIL Contacts. This issue has not yet been solved for years already! Why? Do you run out of storage space to hold high resolution images?
2. The app drawer icon position in the button bar cannot be changed. I hate that thing, because I can't put Phone app there.
Why? If the argument is to never loose the app drawer, at least give ability to change the position.
3. Request Desktop version on the web browser doesn't stick!
Grrrt...!
Sent from my Nexus S using XDA App
gogol said:
To add the injuries, here are some things that are bad in ICS:
1. Contact photo is still low resolution after synced with GMAIL Contacts. This issue has not yet been solved for years already! Why? Do you run out of storage space to hold high resolution images?
2. The app drawer icon position in the button bar cannot be changed. I hate that thing, because I can't put Phone app there.
Why? If the argument is to never loose the app drawer, at least give ability to change the position.
3. Request Desktop version on the web browser doesn't stick!
Grrrt...!
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
lol. Grrrtt.
Sent from my Galaxy Nexus using xda premium
To sum up your entire post: Nothing's perfect.
We know. But Google has done a superb job fixing many things, and hey will continue to improve in new updates to 4.0.
mike freegan said:
First off; I love Android. I think that Ice Cream Sandwich has led to a greater harmonisation of the Android operating system and adds a bit of polish to something functional. Google's apps are starting to feel like they belong together, rather than giving a sense that they're being produced by different teams who have little contact.
However, I'm no fanboy. I don't buy a product and deny that it has flaws just because a certain company produced it *ahem *. So here it is; one humble man's opinion on what's wrong with Ice cream Sandwich.
1. Blue theme.... really? There's a reason that designers avoid blue-on-black. It offers poor contrast, and looks cheap; much like the Geocities sites of the 90s. The blue taskbar and app icons used in ICS just don't go with... well... anything. It's all well and good being able to customise your home screen, but when anything except a blue background clashes it's all a little redundant.
2. The stock icons themselves are disgusting. We all knew this from the leaked screenshots, which forums were praying were fake. Mostly, they just don't look like they belong to the same set. There's no consistency. Half are blue, half are not. Some are three dimensional, and some are traditional, flat icons. Some are different sizes. They just don't work. They look cheap, childish and don't match the 'magazine' style of the UI overhaul. It's like someone realised at the last minute that they'd forgotten to redesign icons, so just did a Google Image search and used the first of each that they found.
3. Google Plus pages won't open in the Android Browser. This one is just plain embarrassing. Google's flagship device can't view Google's new hub outside of the restrictive app? The browser just panics and shuts down with no option to report it. Did no-one test this?
4. Google Talk isn't in the sharing options. That's right, click on the share icon within an app and it'll show you every way of sharing except Google Talk. Following the above, it seems like Google is boycotting their own services.
5. Speech to text for UK language setting is insane. After a few words, it seemingly switches to using your contacts directory as a dictionary, rather than real words. You end up with a full sentence made entirely of surnames and forenames. I cannot believe that no-one tested this.
6. Removing the search key doesn't just remove the ability to search from some apps; it means that you can no longer assign functions to long press, or use voice command from any app. You have to return to the home screen each time. This is a huge step backwards.
7. Similarly, this has led to a non-removable search box on the home screen. Not only does it take up space, but the white icon doesn't work on a light background. The customisability of Android has just been taken down another notch. Sure, you can use a 3rd party launcher, but with no search button, you need the box there for searches.
8. A minor point, but Android can't seem to decide if going for a futuristic hologram look, or the Windows Phone 7 style magazine layout. It's like Mathias Duarte turned up, and they said “Make our OS beautiful... but it still has to look like ugly old Honeycomb (TRON)." All in, it just feels a bit cheap and confused.
9. The soft keys which Google has opted for in ICS are not well positioned. The home key is far too close to the space bar, which is infuriating when typing.
10. The action bar is horrific to use. It means that the menu and search keys jump around the screen. So you're in the Facebook app and want to see the menu. Where is it? Well it's not where it used to be and there's no action bar. Oh wait, three dots have appeared in the soft-key bar. Ugly and inconsistent, but OK.
Switch to messaging. Where the heck is it? Ah it's in the top right now! The little scamp.
Now you're in Gmail. Where is the menace? I know you're here somewhere... Ah, there! In the action bar in the bottom right. Android Market: back up top! There is just no consistency and it makes everything feel disjointed and unpredictable.
The action bar essentially negates the large screen on the Galaxy Nexus. The row of soft keys, plus the action bar actually leads to a lower proportion of screen space for the app than on previous versions of Android.
11. Cut, Copy & Paste: What the hell were they thinking?! This doesn't just jump around based on app, but depending on which page of an app you're in. And even then, the buttons are different every time.
Take Gmail for example. Copying text from the body of an email: a menu appears in place of the action bar at the bottom. However, in the 'compose' screen this menu appears at the top, but with different icons. Another 'paste' button (but not using the paste icon) also appears above the selected text, but no cut or copy buttons. If you try and make a selection from a link, a long press summons a pop-up dialogue where paste is an option. That is four ways of pasting, just within the Gmail app.
Not to mention, that they've opted for icons with no words. Unless you're accustomed to using old Windows machines, this may as well be code. It's like it's intentionally trying to confuse you.
12. Relationships with app vendors must be non-existent. If I was releasing an update to a platform which relies upon people being able to install apps, I'd make sure that the most common apps work on the new platform before release. This could involve providing phones and assistance to the big names. As it stands, neither Facebook nor Whatsapp (two of the top 5 most downloaded apps) work. Both of these are communications related. I feel cut off from the world. I'm sure this could have been sorted before release. Swype is another big name that doesn't support the screen resolution.
Google launched the Galaxy Nexus weeks ago. Facebook was initially unusable due to the absence of a menu button. The app was updated today to a version akin to the iPhone. However, the drag-to- refresh animations don't work as they should, and the damn thing will alert you of 'new messages' every 30 minutes if you have any unread, regardless of whether or not they are new. Atop this, Facebook will still not sync with official Google devices as Facebook does not properly use Google's contact API. Rather than being stubborn, Google should be helping Facebook, or seconding engineers, as they know full well that the majority of their users will require his service.
I appreciate that a lot of this is out of Google's hands, but this is just a warning to early-adopters – be prepared to lose the services you use most.
13. The browser is still useless with forms. Try entering text in a field. It'll type past the edge of your viewport and you can't scroll to the cursor. The viewport should follow the cursor. You can't zoom in and out because you can't get 'hold' of the web page due to the full-screen text entry field.
14. Horizontal lines everywhere. Did I mention that text fields are now horizontal lines? Text boxes are indistinguishable from divides and text doesn't sit on the lines so you never know where one ends and the other starts.
As I said, all in, it is an improvement. However, there is a heck of a lot of room for improvement. There is still a feeling that things aren't really designed, or connected; just a bit haphazard. I'm just hoping Cyanogen pulls something wonderful. For the standard consumer, the experience aspect is still playing catchup with Windows Phone and iOS.
Click to expand...
Click to collapse
1. Don't care .the only thing that is weird is white background in people app. I'd prefer it to be black like in missed call section.
2. Really? Icons brother you that much when you can change them?
3. The whole google isn't working properly in Android browser. Try searching for images in desktop view and tell my chow do you change to larger images ... this is issue that needs to be addressed directly to Google its not a browser issue
4. I presume you're an American. Here on the old continent we don't use gtalk. Well at least none of my friends is using this. We have things like Skype which is far more popular in EU
5. I'm guessing you're from Texas then . Well my accent isn't really British and everything I date 9 out of 10 times is spelt correctly. Ha I can even say that I use dictation more than actual keyboard. Its easier for me to say the text message then type it especially with my second language which Android keyboard does not have dictionary. So I can speak in either one of the two of my languages and its veeeeeeery accurate
6. Blame the developers not Google. They should be ready for new os
7. I love the search box its easy and accessible.
8. I love tron design. However I have to agree its a bit of hit and miss when it comes to design but colours can be changed in custom roms I bet that CM team will do it .
9. Wtf are you taking about. I'm typing this msg and didn't press home bar even once. Anyway try taping between space bar and home button .... it won't even work. Have you got arthritis?
10. Don't see problem here either.
11. Anything with action bar that you don't know what it does just press and hold on the icon there will be pop up window.
12. Again blame developers. Look at rovio. They could update their games at the same time for all devices and os but they choose not to. If the developer can be bothered to update his app in timely manner than who's fault is that?
13. agree with that.
14. Huh?
Sent from my Galaxy Nexus using xda premium

Hide input panels with setting configuration?

Is there a way to hide certain input panels on the window form using configuration or config file of some sort?
For example.... let's say in my database I have items with 12 possible fields in each (Name, LastName, Age, Occupation, Location.......etc).
But what is a user of application only wants to fill in 3 fields every single time (for example - LastName, Age, Location)? Leaving others in place when user doesn't needs them is an extra clutter. So how can I hide or disable those input panels based on user's preference on which fields he wants to use?
--
I think I found a way to hide items by setting Visible boolean.
Code:
this.txtName.Visible = false;
this.lblName.Visible = false;
this.txtOccupation.Visible = false;
this.lblOccupation.Visible = false;
However, how can I move up other fields between or below them? Currently hiding just creates empty spaces.
You can turn the textbox off completely by setting its enabled property to false.
You can then move other textboxes and labels over it by setting their Location.X and Location.Y properties.
You will have to keep track of where everything is on the screen, and what is enabled and what isn't.
stephj said:
You can turn the textbox off completely by setting its enabled property to false.
You can then move other textboxes and labels over it by setting their Location.X and Location.Y properties.
You will have to keep track of where everything is on the screen, and what is enabled and what isn't.
Click to expand...
Click to collapse
Thanks.
Do you know if there is an easy way to move everything up? (lets say I make first item invisible and want to move the 10 items below up) Or will I have to call everyone individually to move up?
Also.. Is there away how I can use TabIndex to call those forms?
There are others ways to accomplish what you are looking for, but no easy route to it.
They all end up as broad as long. You either spend time during the design stage, creating an array of possible tabbed forms to be used by the program later, or spend time designing the program to deal dynamically with the fields required. The latter of the two is harder to do, but it is far more elegant.
Sorry, but there is no silver bullet.

Categories

Resources