Author Topic: Now Full Screen  (Read 3358 times)

0 Members and 1 Guest are viewing this topic.

Peter

  • Guest
Now Full Screen
« on: August 10, 2014, 05:50:39 AM »
Deleted.
« Last Edit: January 28, 2015, 03:48:14 AM by Peter »

Mike Lobanovsky

  • Guest
Re: Now Full Screen
« Reply #1 on: August 11, 2014, 06:21:26 AM »
Hi Peter,

Changing full-screen resolution uncontrollably to any setting other than its native resolution ruins the disposition of desktop icons on multiple-monitor setups. My workstation has three monitors with over 150 icons on my desktop.

This is the exact reason why I haven't downloaded a single one of your submissions from this thread.

Can you please add a prompt to your programs that would ask the user if they want to allow the programs to run in a full-screen mode? In case the user refuses to select full-screen then it would be reasonable to let the program run in a windowed mode.

You will have a somewhat broader audience by doing things properly.

Aurel

  • Guest
Re: Now Full Screen
« Reply #2 on: August 11, 2014, 06:24:51 AM »
cool thing Peter... ;)
this reminds me about fascinating pyramid structures and golden section
http://www.dudeman.net/siriusly/cyd/city.html

Mike Lobanovsky

  • Guest
Re: Now Full Screen
« Reply #3 on: August 11, 2014, 08:17:38 AM »
OK,

My message talks about a genuine windowless graphical full-screen mode. Now I see that what you actually have here is in fact a fixed-size window.

So it was just a misunderstanding based on improper terminology. A fixed-size window is not a graphical full screen.

Thanks for the feedback though. I think now that I have your assurances, I can try your code on my monitors. Otherwise, I couldn't and wouldn't.


[UPD] I'm sorry to say it but your bitmap scripts crash for me. The offending function is peek(). I'm using the latest build of O2 dated August 7.

Mike Lobanovsky

  • Guest
Re: Now Full Screen
« Reply #4 on: August 11, 2014, 01:32:15 PM »
"Freeebitap" is wrong and must be  "Freebitmap".  no clue why !

I suggest checking your keyboard for possible breadcrumbs, dried beer or coffee spots, and peanut stumps. :D

Mike Lobanovsky

  • Guest
Re: Now Full Screen
« Reply #5 on: August 11, 2014, 01:46:52 PM »
And no Peter,

Your fix did not work for me. Please see the picture below. It is the same for both bitmap scripts.

The error message says your calls to peek at line 36 of both scripts are not correct. peek expects three arguments but you are passing only two arguments.

Declaration:
Code: [Select]
' asm.inc, line 89:
! Peek         Lib "asm.dll" (sys memadr,offset, byte value) as byte

Calls:
Code: [Select]
' 1st BMP script, line 36:
r = peek mem[id],z+0 ' and 2 more calls below

' 2nd BMP script, line 36:
r = peek memory[id],z+0 ' and 2 more calls below

Your PC memory seems to tolerate the bug. My PC crashes.



P.S. Is your beer virtual too? What a pity. :)

.

Mike Lobanovsky

  • Guest
Re: Now Full Screen
« Reply #6 on: August 11, 2014, 02:04:36 PM »
FYI:

You supplied these examples with an outdated version of DLL and asm.inc.

Your latest upload Julia Fractal Big contains the zip that should be used with these two scripts too. Here peek is declared differently:

Code: [Select]
' new asm.inc, line 88:
! Peek         Lib "asm.dll" (sys memadr,offset) as byte

Mike Lobanovsky

  • Guest
Re: Now Full Screen
« Reply #7 on: August 11, 2014, 03:16:44 PM »
Thanks Peter,

Have a nice night.