iOS (iPad) Screen BUGs (round corners, windowed, buffer video????)

[DaCarSoft]

Yes! I suppose...

Let me test a little...


Do you have an extern pointer like "gpiCadeView" for the "glView"?


EDIT: I suppose that "gpGLB_MainWnd" could be useful.

[spacefractal]

Also basic should been basic, that also inline calls using them should been keept as minimum, elsewise its would begin to been compliced for more for us. So its can mightbeen not been a 100% fix.

Its seen the iCade windows is not rotate correctly after the costume rotation call (just like Android). Howover if its did resize and its did keep the corners to the corners, then its would been much less notiable and acceptable. Its could been done example under SETORINTATION, so the UI could rotate directly too under that, and also resize the iCade window too here.

That would been the best fix to that.

Also another way yo do is, iCade is treated like a joypad, so possible to disable and init a joypad would been cool too. Also doing that example with ENABLECONTROL(JOYID, BOOLEAN). This would also not break any compatiblle and I could reinit iCade after resume call with ENABLECONTROL(1, TRUE) to reinit it again (if iCade have id 1).

[Kitty Hello]

the iCade also offers INKEY$ for bluetooth keyboards.

[DaCarSoft]

Hi again.

I just tested it (hardly)...

I can't replicate the fail in my project because I suppose that I can't obtain exactly the same "iCadeReaderView".

I'm using this code for testing (in addition to your "application didFinishLaunchingWithOptions:" from your post, Gernot):
https://github.com/scarnie/iCade-iOS/tree/master/iCadeTest/iCade

After testing it, I don't see any problem in the iCade from Scarnie...   It only shows rounded corners because of a nib file included in its info.plist

May be a problem inside the iCadeReaderView controller...   or inside the EAGLView code... or a wrong call to "makeKeyAndVisible"...

I suppose there is no bundled "nib" files into the .a GLBasic's framework...


Is there any way that I don't know to access to gpiCadeView pointer?



EDIT: It also appears that the last version of the code from "scarnie" solves a problem related to background/resume...

Spacefractal: I also think that BASIC is BASIC (I love GLBasic) and I also think that should be reduced when it is possible the inline calls... But for supporting certain functions from iOS you need to use XCode if GLBasic does not support it... Because of that I like GLBasic: You can expand it with wrappers... I did wrappers to use the iOS keyboard (supporting Bluetooth keyboards also) and alerts, and I did my "iOSSetOrientation" wrapper because Apple shows in its policies that apps have to support (totally, including the bottom multitasking bar) two or more device orientations... I don't know any app rejected because of this, but these are the Apple policies... I feel more comfortable implementing this.
The iCade appears to cause "visible" problems and I think that iCade is not a device largely sold, I only think that implementation could not be a priority if it brings problems. Or it could be done in other "invisible" way... But I agree with the idea of make the effort to try to have all things working first.

[spacefractal]

Apple have rejected apps that dosent support both landscape modes on iPad (if its a landscape game), but how you doing that by IOS system call or by software is irrerevent (its depend on app, and often games just using software method, since they not using IU calls).

Gernot could of course do a iOSSetOrientation call to the SETORIENTATION (so eventuelly UI would rotate too), and he might face the iCade issue as the previous screenshot (but easier to fix when he can invoke it). Then we would have a much better iCade support since the corners would now allways on the bottom and resized correctly (again to been done under that command). So all fix could really been done under that command, which I see the bug is really there. Its would been a very small issue if they are gone or not (due they allways on bottom as they should amd UI should not been broken anymore even they still might been shown).

iCade is a very great and well buildt arcade cabinet and I have it and its a highely recommered product and cool to support it when you can and if the game using arcade style controls. If does, you need to support it.

Best is simply disable it by default and let user enable it from the game options (some games require it). Then its would been fine with me.

[DaCarSoft]

Apple wants that programmers don't break the usability of their devices.

They want that every app support all their Human Interface Guidelines, it's to say:

The four fingers swipe up/down must be working correctly in your app, according the orientation of the image that user sees...   All apps have to support multiple orientations fully working...    They suppose that programmers have full access to their tools (XCode, Safari/webkit) to fully support this.
Just the same that if your app requires the use of the Internet, you have to detect when the network is unavailable and you have to notify this fact to the user...
Just the same that you have to make match your 512×512 iTunes Store icon with the 57x57 iPhone icon, the two icons have to be the same image, or very near to be the same...

There is so many rules that do not appear clearly in their HIG, but they are supposed to be obvious, and you have to play their rules...
You can't claim "App X does this but is already in the App store" as an excuse when Apple rejects an app. They will not accept it as a valid justification.


Sorry if I'm going offtopic

[Hark0]

This is starting to get too complicated for me now.
What can I do? Hide the iCade view? Do you want a pointer to it? Would that help?

EASY!

1 Delete ALL references to iCade in GLB.
2 Make new post on forum-snippeds and paste *.m,*.h, *.* wrapper files needed for iCade.

Other users can paste his own wrapper files for other things like EMail, camera roll, keyboard, alerts, bt devices, etc

[spacefractal]

Those 4 finger gestures is actually very annoying and they are not on guideline at all (i diddent find that). I guess it's did not work as intended on iPad, due it's interfered too much with 2 player and music based games (they often use 5-6 fingers touchs here).... I disabled quickly due that. So it's don't works with games, but different story with applications of course.

Yes it's offtype now, and all we can is see the setorintation bug to fixed. The bug is all rely in that. It's more important by now.

[DaCarSoft]

It is not only a problem related to iOS orientation through wrappers, I suppose:

http://www.glbasic.com/forum/index.php?topic=7867.msg65671#msg65671

There is also people hiding corners doing things like this:

http://www.glbasic.com/forum/index.php?topic=7867.msg66155#msg66155

Or this (I suppose, but this may be not because corners):

http://www.glbasic.com/forum/index.php?topic=8038.msg67427#msg67427

[spacefractal]

Its the http://www.glbasic.com/forum/index.php?topic=7867.msg65671#msg65671 issue that could been fixed by SETORINTATION, so its doing a iOSSetOrientation call when the command is invoked, and its should also resize the iCade window after that correctly (so you not get the previous issue). That could also fix the nonerespons iCade issue as well when a app is resumed.

When doing that, then the corners should been present on the bottom, and the same is with eventuelly keyboards and other UI calls. I think this is the best to have both worlds so we still can have iCade support without breaking UI calls. Those who want to hide corners could then eventuelly use the http://www.glbasic.com/forum/index.php?topic=7867.msg66155#msg66155 trick after that.

PS. Possible by disable iCade support for advanced users could eventuelly been done by some function in classes/main.m or by a classes/disableicade.m)...

[Hark0]

In my tests SETORIENTATION no fix nothing!!!!




I think like @Dacarsoft; the BEST WAY are DELETE all related to iCade in GLB and offers support for iCade with wrappers (*.m, etc files).

(Fix bug corners with images are a TEMPORAL trick... not a PROFESSIONAL SOLUTION.) 


Regards!

[javiero]

In my tests SETORIENTATION no fix nothing!!!!




I think like @Dacarsoft; the BEST WAY are DELETE all related to iCade in GLB and offers support for iCade with wrappers (*.m, etc files).

(Fix bug corners with images are a TEMPORAL trick... not a PROFESSIONAL SOLUTION.) 


Regards!

+1

[spacefractal]

so before going rage and such, so calm down and not going to been upset (its close doing that when you formatting text like that).

So in the nice short time fix, is still fixing SETORIENTATION as I wrote before (the missing iOSSetOrientation call) and rework the wrong rotated iCade window). Should been quite easy to do. Then the issue would been became pretty very very small.

A better long term fix is adding the ENABLEKEYBOARD command for disable/enabling bluetooth keyboards (possible to enable/disable keyboard/iCade supports without wrappers). Here its might take some time me think to get it work correctly on all OS (Android, WebOS and iOS as primary target).

In timeline usage I still think the short time fix is easist first, even its NOT perfect. Its a comprimise.

EDIT: Sorry I removed a post, as I did not want to offensive some people, which was not intendend to do that. Sorry about that.

EDIT 2: The code Gernot posted, could that not just been moved to a launch.m file? Then if people want to disable iCade, they could just comment the iCade relavent code out? I really dont think its break INKEY$ at all.

[Kitty Hello]

dacarsoft is currently trying to help me fix this issue. I know the urge and I hope to provide a fix, soon.

[spacefractal]

Personly i dont care about them as long they displayed correctly in the corner. In Greedy Mouse they are barely not noticeable anyway or thinking about it at all. I think, it's a iOS charm :-)

That why the SETORIENTATION thing, which could also fix the notifaction center issue as well I posted some while ago....