My MIDlet uses Forms as well as Canvas. When I navigate into a canvas, my Nokia 5800 goes into backward compatibility mode and starts showing all those buttons. How do I avoid it.
P.S. I am not making use of any button inputs.
You need to configure your jad file
There are various options, the most likely one you require is
Nokia-MIDlet-On-Screen-Keypad: no
The other options are
Nokia-MIDlet-On-Screen-Keypad: gameactions
Nokia-MIDlet-On-Screen-Keypad: navigationkeys
Nokia have a full explanation on how this affects your application here
http://wiki.forum.nokia.com/index.php/Using_on-screen_keypad_in_MIDlets_in_S60_5th_Edition_devices
put the following line into our JAD:
Nokia-MIDlet-On-Screen-Keypad: no
Related
Android studio missing take screenshot and video option is missing in latest version(3.4.1).
Ctrl+s is working but i am unable to get screenshot in real device(attached via cable) use Ctrl+s.
Any other way to taking the screenshot of real device and store in to system?
Click on setting icon on top and click "Show Toolbar" like in below pic
You can take photos/videos under Logcat, using these buttons. Sometimes they are hidden in a little drop down, which is indicated by two little arrows instead.
Unless you mean taking screenshots and saving them on the device. In which case just use the device's mechanism for taking screenshots?
I have a technical doubt on an ePub3 job and thought of checking with you all and get your understanding and advise on it.
For one of my German client, I have created a ePub 3.0 re-flow with interactivity, we have used all the interactivities to work on pop-ups (Non-linear content) and it works well on iPad iBooks 3.2, as the initial request from client is to work only for iPad.
I understand that a latest Apple spec (iBooksAssetGuide 5.1 Rev 2) now says that “Develop scripts that perform well on both Mac OS and iOS devices: Interactivity on desktop computers requires input from a mouse while interactivity on iOS devices require touch input”. I’m not sure whether there would be any problem while this job goes into the Apple iBooksstore, due to the latest spec.
It would be of great help, if you all please share your idea’s / view to this problem.
Regards,
John.A
Great question. With the latest version of OSX (Mavericks) running iBooks as well, there are a few things that need to be considered when using touch interactivity in ePub3 books. The most important (and relevant here) of these is making sure you are firing mouse events as well as touch events: because they behave differently.
The most robust solution that I have found to date is using JQuery or Quo's "tap" event: as it will fire with both touch and mouse events! However, if your code digs deeper (IE if you you use events like "touchstart", "touchmove", etc.) you will need to use the corresponding mouse events to insure functionality on the desktop.
Tap.js is a great little library for stuff like this: http://alxgbsn.co.uk/2012/03/12/tap-js-a-lightweight-tap-event-javascript-plugin/.
You should also be aware that iBooks for OSX behaves differently for many features (especially when it comes to external media content and dynamic loading of content), so you should never rely on OSX only when testing...
Good luck!
Just wanted to know if it is possible to open regular XIB files from new Xamarin's storyboard editor? Switching back and forth between Xamarin and Xcode is a bit inconvenient, and the new editor looks really nice; however, Storyboards have a few drawbacks and it is a pain to use them for our projects.
Any ideas re availability of this?
The plan is to add support for editing .sib files in future versions of Xamarin Studio.This will likely not happen in time for the first release with the iOS Designer (i.e. version 4.2), but I think it would be reasonable to expect that version 4.4 will have support for editing .xib files.
As of right now, no. I think it might be because of the complexity of the underlying XML but I'm not 100% sure. You can always create or upvote it on uservoice: http://xamarin.uservoice.com/forums/144858-xamarin-suggestions/suggestions/2700302-a-monotouch-xib-editor.
Using stand-along Xib files is now available, you can learn how to do it here -
Using Xamarin Storyboard Editor to edit XIBs
I had a problem in displaying icon in button along with the Text in MFC application.. after reading lot of arctilces I got a solution for that and it worked great.But when I tested my application in win xp(SP2)..it suprised me by not showing the icon..Check the below code which i used to display the icon along with a test in button..Please let me know if there are any fix for this issue..waiting for your replies
HICON addIcon = (HICON)LoadImage(AfxGetApp()->m_hInstance,MAKEINTRESOURCE(IDI_ICON4),
IMAGE_ICON,0,0,LR_DEFAULTCOLOR);
SendMessageA(::GetDlgItem(m_hWnd,IDC_ADD),BM_SETIMAGE,IMAGE_ICON,(LPARAM)(DWORD)addIcon);
If you're using VS2008 (you should), use CMFCButton from the Feature Pack. It has much better support for bitmapped buttons.
I can confirm that i can't get it to work (on Win2003, my primary development machine) and a brief search on the web found many complaints but no viable answers.
My only suggestion would be to do an ownerdraw button - handling the WM_DRAWITEM message is not difficult and may resolve this issue for you across the board.
see "Native Win32 Theme aware Owner-draw Controls without MFC"
How (i.e. using which API) is the virtual keyboard opened on Symbian S60 5th edition? The documentation seems to lack information about this.
You are right, this should obviously be a published API and it should be highlighted in the documentation. No such luck.
If you are using one of the platform native controls, the virtual keyboard will automatically popup when the user accesses a text-editing control.
If you are making a custom control, you need to deal with its selection by adding your own version of the virtual keyboard: make a new text-editing, window-owning virtual keyboard look-alike custom control with the right buttons. Reuse it accross all your applications. One day, Nokia will realize they have made an obvious mistake and make the API publicly available.
If you are using direct screen access, well, you wouldn't exactly expect the very s60-looking virtual keyboard to popup out of nowwhere. Again, draw a nice image on the screen to let the user know where the virtual keys are and react to pointer events. This is going to be less reusable unless you build a good amount of customization (background, button edges...) into it.
EDIT: Nokia may be relying on Qt to fix this issue. I would expect the control to be part of the current 4.7 version of Qt.
Tinkering with focus on a QLineEdit inside custom coded kinetic scroll area, I've had a simmilar problem (how to open virtual keyboard manually). Then, I found it, this obviously works in Qt 4.6.3 on a C7 Symbian^3 phone:
// lineEdit is an instance of QLineEdit
QApplication::postEvent(lineEdit, new QEvent(QEvent::RequestSoftwareInputPanel));
Before that, I also had to post a QEvent::FocusIn event to that same lineedit, otherwise the QLineEdit did not update the content from virtual keyboard.
Hope this is helpful. I lost hours.
Thank you tihi, very useful tip! There's also the "close virtual keyboard" event that can be triggered:
QApplication::postEvent(lineEdit, new QEvent(QEvent::CloseSoftwareInputPanel));