One of the very first things I solved with RFO Basic.

How?

 

Have you reviewed this?
https://developer.android.com/guide/practices/screens_support

Thanks for the reminder i meant to read that, i just hope they have examples i have no idea how to start yet.

 

How?

Basically with this, from the manual by Nic Antonaccio:

11.15 Scaling Graphics to Fit Different Screen Resolutions
RFO Basic includes a simple feature to scale graphics to fit properly on screens of any resolution. The following code, taken directly from the De Re Basic Manual demonstrates how to scale your screens. All you need to do is set the initial 2 values (di_height and di_width), and the entire graphic application will be scaled in relation to those set size, no matter how big or how small the screen dimensions are:

di_height = 480
di_width = 800
gr.open 255, 255, 255, 255
gr.orientation 0
gr.screen actual_w, actual_h
scale_width = actual_w / di_width
scale_height = actual_h / di_height
gr.scale scale_width, scale_height

 

@MrAl

To avoid confusing issues, I am posting separate from the above.

Prior posting the previous, I revisited quickly the subject and got surprised.

My experience with RFO Basic, was made almost 5 years ago! and recently, after some long time, in April 2019, the next version has been issued (1.92).

The maintenance (development?) seems to be in the hands of somebody else than the original author, Laughton.

It seems that two varieties coming from the original language are being developed in parallel.

The existence of different packages, software doing similar things oriented to PCs or tablets makes for confusion. Sometimes, they call it RFO Basic, or BASIC! or Basic! or rfo-basic or ...

Even the fact that there are plans to issue a version that could be again offered through Google Play but unable to deal with SMS. Here, it all boils down to the Google's policy regarding the software asking for permisions when installed.

In the last weeks I was thinking to revisit the whole subject but the above appears rather discouraging to me; too much info to wade through.

And then Tapatalk!!

 

https://developer.android.com/training/multiscreen/screendensities

 

I forgot I uploaded this in YT.

 

https://developer.android.com/training/multiscreen/screendensities

Yes thanks those vids seem to help explain some things.
The problem i was having was for a smaller screen some things would move off screen.

Also, in landscape mode much would move off screen. I found ways around that but i an wondering now if it is better to publish some apps as for portrait view only because in landscape view everything gets squashed, and if i design for landscape then everything gets spread out too far in portrait view.
I am thus thinking that each view should have it's own purpose, although conflicting with that ideas is that some people may wish to use their devices in the view of their choice anyway. So i havent decided what to do about this yet.

 

@MrAl

To avoid confusing issues, I am posting separate from the above.

Prior posting the previous, I revisited quickly the subject and got surprised.

My experience with RFO Basic, was made almost 5 years ago! and recently, after some long time, in April 2019, the next version has been issued (1.92).

The maintenance (development?) seems to be in the hands of somebody else than the original author, Laughton.

It seems that two varieties coming from the original language are being developed in parallel.

The existence of different packages, software doing similar things oriented to PCs or tablets makes for confusion. Sometimes, they call it RFO Basic, or BASIC! or Basic! or rfo-basic or ...

Even the fact that there are plans to issue a version that could be again offered through Google Play but unable to deal with SMS. Here, it all boils down to the Google's policy regarding the software asking for permisions when installed.

In the last weeks I was thinking to revisit the whole subject but the above appears rather discouraging to me; too much info to wade through.

And then Tapatalk!!

I would supoose that vid you posted is in real time and you see how slow it is at plotting that data. That's one thing i did not like about it, although it makes a very nice plot line

 

Yes thanks those vids seem to help explain some things.
The problem i was having was for a smaller screen some things would move off screen.

Also, in landscape mode much would move off screen. I found ways around that but i an wondering now if it is better to publish some apps as for portrait view only because in landscape view everything gets squashed, and if i design for landscape then everything gets spread out too far in portrait view.
I am thus thinking that each view should have it's own purpose, although conflicting with that ideas is that some people may wish to use their devices in the view of their choice anyway. So i havent decided what to do about this yet.

I'm not sure if there is an official standard but many technical apps seem to lock the view in portrait for single hand use in a phone sized device. I hate rotations if I need to use an app while crawling inside a machine sideways.

 

I'm not sure if there is an official standard but many technical apps seem to lock the view in portrait for single hand use in a phone sized device. I hate rotations if I need to use an app while crawling inside a machine sideways.

Oh that's interesting. Yeah that is what i thought too, that some apps just dont look right in landscape view, and some wont look good in portrait mode.
Not sure how to lock the view yet though.