I created a CAknEnumeratedTextPopupSettingItem control using Carbide.C++ 2.7 as it looks below:
(known as enumeratedTextPopup control in Carbide.C++ IDE )
And I'm using Symbian S60 5th Ed SDK; And Targeting Symbian S60 5th Ed, Symbian^3, Symbian Anna.
Now I want to know how to make this control follow one tap style ( One tap to highlight and select ). Is there any flags needed or properties to set ?
The way the control works is, one tap to highlight, and another tap to select.
Best Regards.
Symbian S60 5th Ed doesn't support one tap to activate and select an item; This feature is supported
by Symbian^3 and forward.
Symbian^3 Application Developer Library
S60 5th Edition introduced touch support feature with double-tap to maintain binary
and source code compatibility with the existing S60 3.x applications.
Symbian^3 enhances the touch support with single tap for achieving better usability
and development of platform and 3rd party applications. The supporting UI is based on
direct manipulation and is not focus driven, which means that a single-tap on the
device selects and activates an event.
So, if the application created by S60 5th Ed and targeting both Symbian S60 5th Ed and Symbian^3,
Then "Slider" control could be used in place of "enumeratedTextPopup".
Find more details about migrating application from Symbian S60 5th Ed to Symbian^3.
Related
I've started doing Windows 8 Store app development for some projects at work, but I do not have a touch screen device of my own at home. If I write a personal app for submission to the store, I must use my own hardware since I can't use the work computers for personal projects. My concern is getting into a situation where I submit an app to the store, then have touch-screen users describing issues that I can't replicate on a non-touch-screen device.
Are there any functions or capabilities or interactions that behave differently in a Windows 8 store app when using touch vs. using only a mouse? Are there any scenarios I could encounter where I would be at a loss to reproduce or troubleshoot a user's problems if I do not have a touch screen?
As Konstantin suggested, a tablet is strongly recommended.
The next best thing is to use the device simulator in Visual Studio. It will let you change screen sizes, and allows you to simulate basic touch gestures with the mouse. This MSDN link has more info: Testing Windows 8 apps using Visual Studio 2012
Microsoft have introduced events that are pointer agnostic meaning that they should function the same way regardless of whether you are using a touchscreen, a mouse or a pen. Those are the MSPointer events. Here's some documentation. Using event handlers for these events mean that you should not be getting complaints from users about the touch friendliness of your application. However I still strongly suggest that you acquire a surface and test your application on it. Not just for the touch friendliness but also because of performance differences.
Is there away to copy a screenshot directly into an Adobe Air (2) application?
Kinda like this: User presses the "print screen" button and the screenshot shows up in the app.
Also I'ld like to know if pasting via keyboard or right-click work for that?
I'm new too AIR.
Best, John
Yes, it can be done.
But no, not directly from Air, unless you wish to capture parts of your own AIR UI (which should be no problem as these are within the scope of the AIR Application)
To capture the whole screen you would need to use an ANE (Adobe Native Extension) which can be written
both for iOS and Android devices and used from within AIR via an API.
Introduction to ANE Development:http://help.adobe.com/en_US/air/extensions/air_extensions.pdf
The following post discusses on the way by which an Air ANE can capture a screenshot (which is technical and relevant for developing such an ANE for Android)
How Native Extension take screenshot on Android device?
Other then this you might try a workaround, that is, instructing the user to capture using his own device's capture combination, then simply ask them to select the file from the Gallery, if indeed this is your intention...?
How can I create a multiple check list items control as in the picture bellow using Symbian ?
I'm going to use this control in my SettingList view.
I'm using Carbide.C++ 2.7 , And Symbian S60 5th Ed SDK.
Many thanks in advance.
You need to use the symbian lists API. Specifically you need the MultiSelection list box.
http://library.forum.nokia.com/topic/S60_5th_Edition_Cpp_Developers_Library/GUID-759FBC7F-5384-4487-8457-A8D4B76F6AA6/html/Lists_API4.html#topic3.10
In Symbian S60 (not QT), if a menu item is not applicable to my current menu state, can I make it appear but greyed out, or is it always removed from the menu (i.e. invisible)?
In Symbian S60, CEikMenuPane::SetItemDimmed() removes menu options.
In the now defunct Symbian UIQ, the same function dimmed/greyed out menu options.
See this book.
So just use that function and have them removed in Symbian 60 (which has merged and is just called Symbian nowadays).
I never saw this in past 8yrs I am developing on Symbian, the item is always hidden. I had made custom menu on my own - but I cannot advice this approach. With Symbian source code I could probably hack it for your application, but the effort will not be paid back.
BR
STeN
I would like to create a preferences window like in the standard Mac OS X apps (Safari etc.). I have found resources like DBPrefsWindowController from back in 2008 that matches the Apple HIG.
Just wondering if there is a new way to accomplish this? I can't locate any standard windows in Interface Builder so I assume Apple doesn't provide those, nor can I locate a official Apple sample code for providing this standard UI.
Thank you
It seems DBPrefsWindowController is no longer available.
For now, I would recommend the up to date RHPreferences framework.
Available on GitHub. BSD Licensed.
It’s a simple and easy Preferences window controller with multiple tabs for your next Mac application.
It also provides:
Auto resizing between different sized tab views (With animation)
Custom NSToolbarItem support
Persistence of the last used tab
Support for placeholder NSToolbarItems (eg NSToolbarFlexibleSpaceItemIdentifier & NSToolbarShowFontsItemIdentifier)