ios - Does a width of 44 pixels equate to the same physical size for all devices? -

-

i work based on screen size of iphone 6 1136x750 pixels @ 326 ppi. i'm more concerned physical size of buttons (for reason) rather digital sizes.

if button has width of 44 pixels on iphone 6 , physical width of 0.2 inches has same physical width on iphone 6 plus 401 ppi?

if not, isn't supposed violate apple's guidelines? had tested 44 pixels minimum width, bigger ppi same width decreases physically.

is adjusted/scaled somehow?

edit: have feeling i'm being stupid , obvious.

edit 2: original concern across screen iphone 6 can have total of

t = 375.0 / 44.0 = 8 buttons.

while iphone 6 plus can have total of

t' = 540.0 / 44.0 = 12 buttons each button being physically smaller.

the way fix figuring out adjusted width of buttons iphone 6 plus w' = 44.0 px * 401 ppi / 326 ppi = 54.0 pixels.

so, each button on iphone 6 plus should have width of 54 pixels of same physical size.

am thinking correct?

you're right math, points in ios has nothing physical size.

physicalsize = points * scale / ppi

5.5" 44*3/401 ≈ 0.33 inch

4.7" 44*2/326 ≈ 0.27 inch

so in order guarantee same physical size need calculate manually each device, not best practice anyway.

from above formula this:

points = physicalsize * ppi / scale

swift function:

func points(frominches inches: cgfloat) -> cgfloat {     return inches * ppi / uiscreen.main.scale }  var ppi: cgfloat {         //return device ppi }

check this question getting ppi programmatically:

edit:

i still recommend thinking in terms of points, not in terms of physical screen size.


Comments

Post a Comment

Popular posts from this blog

php - How to display all orders for a single product showing the most recent first? Woocommerce -

-
i have password protected page on frontend. on page, want display full list of purchases associated single woocommerce product id. option 1: i've looked through woocommerce docs , , found: wc_cli_order , list_( $args, $assoc_args ) function lists orders. presumably, orders can filtered product id [--=] filter orders based on order property. line item fields (numeric array, started index zero): line_items.0.product_id option 2: i found article , based on customer id. i've modified code based on guesses meta_key , meta_value. $customer_orders = get_posts( array( 'numberposts' => -1, 'meta_key' => '_product', 'meta_value' => get_product_id(), 'post_type' => wc_get_order_types(), 'post_status' => array_keys( wc_get_order_statuses() ), ) ); how display orders single product showing recent order first? here solution put based on these articles: http://www.w...
Read more

asp.net - How to correctly use QUERY_STRING in ISAPI rewrite? -

-
i'm having difficult time , hope guys can help. using helicon isapi rewrite version 3.1.0.104 on our iis server. edit http.conf file , have tried , still fail. this trying do: redirect url: https://www.domain.com/switch-by-version?version=2.8.5.2594 to: https://test.domain.com/load/load.aspx?tver=2.8.5.2594 the version number @ end source url change, , need target url have same version number @ end of url example above shows. i tried following not work: rewritecond %{query_string} ^version=(\d\d?)\.(\d\d?)\.(\d\d?)\.(.*)$ [nc] rewriterule ^/switch-by-version(.*)$ https://test.domain.com/load/load.aspx?tver=%1 [r=307,nc,l] any appreciated! thanks. if it's running in equivalent context of .htaccess , rule shouldn't start / . here's simpler version: rewritecond %{query_string} ^version=(\d+\.\d+\.\d+(?:\..+)?)$ [nc] rewriterule ^switch-by-version/?$ https://test.domain.com/load/load.aspx?tver=%1 [r=307,nc,l]
Read more

angularjs - How restrict admin panel using in backend laravel and admin panel on angular? -

-
https://scotch.io/tutorials/token-based-authentication-for-angularjs-and-laravel-apps following tutorials, try write authentication restrict admin panel, didn't understood how can that. this admin panel, admin panel don't want show , request database unauthenticated users. my laravel-routes route::get('/admin',function(){ return view('index'); }); route::get('/api/v1/employees/{id?}', 'employees@index'); route::get('/api/v1/users/{id?}', 'employees@users'); route::post('/api/v1/employees', 'employees@store'); route::post('/api/v1/employees/{id}', 'employees@update'); route::delete('/api/v1/employees/{id}', 'employees@destroy'); route::group(['prefix' => 'api'], function() { route::resource('authenticate', 'authenticatecontroller', ['only' => ['index']]); route::post('authenticate', 'authentic...
Read more