aldweb

Close I. aldweb

Close II. PC Freeware

Close III. Palm Freeware

Close IV. Palm Shareware

Close V. iziBasic Palm

Close VI. Palm Knowledge

Close VII. Pocket Computer

Close VIII. miniPortail

Special !



Mobile version of
the aldweb Site

m.aldweb.com


Neither French, nor English?

Try one of these flags then:
[de] [es] [it] [pt]
Search




Weather / Spam / www

Lyon Weather


aldweb against spam


Newsletter
To receive news about this website, consider subscribing to our Newsletter.
Subscribe
Unsubscribe
298 Subscribers
Family's web sites

Webmaster - Infos
Friends News
Visits

   visitors

   visitors online

Poll
What do you think of the new design of the aldweb Site?
 
Great !
Beautiful
Average
So ugly...
Results
Post an answer

Thanks for taking the time to write this message.

Your user name :

Your e-mail :

Hide your e-mail address to visitors:      
Note: the e-mail address is protected against SPAM.

Subscribe to this thread :      

You are answering to aldweb who wrote:


Hello Mike,

This new close menu event was indeed added, in version 5.1 and I remember very well of it because I spent hours and hours to implement it!
So, there was a good reason for doing it

This is indeed absolutely required for real time games (the one to thank for giving me the information is Leonard: http://izibasic.aldweb.com/leonard/) that need to know when to stop/start again the animation after the menu was closed. I spent that number of hours because this event is not provided by Palm OS so I had to trick the system to simulate one...

Now, in a way, you are right, the close event is usually not needed if a selection was made and I understand very well your point of view.

But, between the time the selection is made and the time the menu is really closed there might be a few system ticks and the real time game programmer would rather capture the right event... Otherwise some drawing could occur on top of the menu, which is then erased, erasing at the same time what was drawn.

And also, to be honest with you, since my trick succeeded to capture/simulate this close event, I was so happy with it (remember that I spent hours and hours on this topic!) that I'd rather leave it that way.

I also believe that the succession of events is clean this way:
1. a menu is opened
2. eventually, a menu item is selected
3. the menu is closed

Now, in a usual case, all you need to do in a source code is:
1. was there a menu event? (EVENT 1001)
2. what item was eventually selected? (MENUITEM >0)
At this stage, I believed that this change would cause no change in users existing source codes. I always pay very much attention to the compatibility topic so that any source code of a previous version should compile and run the same way with a new iziBasic version.

So, I hope that you will allow me to ask you one question. I ask it to the friend that you are and not at all in a commercial way at all as I should probably do with the famous reviewer at a great web site (dear other readers, you should bookmark this site if not already done: http://www.palm247.com) that you are... well you know my sense of humour!
So here is the question: maybe was your source code not really optimized? Maybe is this the good opportunity to optimize it now? (I cheated, I asked 2 questions!)

You see, I could write a full story on this topic! So, I better stop now!

Cheers,


@+
aldweb


Help :

Code Syntax :

  • <color=CodeHexadecimal></color> enables text colouring.
    Note : Instead of the hexadecimal code (#??????), you can specify the name of the colour(red, yellow, orange, green, blue, etc...). For extra info...
  • <bgcolor=CodeHexadecimal></bgcolor> enables the colored highlighting of a text.
    Note : Instead of the hexadecimal code (#??????), you can specify the name of the colour(red, yellow, orange, green, blue, etc...). For extra info...
  • <b></b> enables the emboldening of a text.
  • <i></i> enables the italicising of a text.
  • <u></u> enables the underlining of a text.
  • <cite></cite> enables quotation inserting.
    Note : You can specify the name of the authors by typing <cite=Author>
  • <code></code> enables code inserting.
    Note : You can specify the language by typing <code=LanguageName>
  • <left></left> enables left align.
  • <center></center> enables center align.
  • <right></right> enables right align.
  • <link></link> enables link inserting.
    Note : You can specify the link URL by typing <link=URL>text</link>. If you do not specify the link URL, the URL will be the one between the two tags.<link>URL</link>
  • <img=SmileyName> enables smiley insertion.
    Note : The names of available basic smileys are : cool, wink, biggrin, smile, frown, eek, mad, confused, rolleyes, tongue, cry. For extra info...

Access keys (under Windows) :

  • Key SHIFT + arrow (right or left) enables text selection
  • Key ALT + 2 enables toolbar selection
  • Key ALT + 3 enables editing zone selection
  • Key ALT + 4 displays Help
  • Key ALT + 5 hides Help
  • Key TAB enables going from one selection to the next
  • Key SHIFT + TAB enables going from one selection to the previous
  • Key ALT + arrow (towards bottom or top) enables folding out of the selected menu
  • Key ALT + arrow (towards bottom or top) enables the folding up of a spread out menu
  • Key arrow (towards bottom or top) enables the browsing through a spread out menu
  • Key ALT + s enables form sending

   |     |  Bold  Italic  Underline  Insert a quotation    Align Left  Center justify  Align Right  Insert a link  Insert Smiley (popup)  Preview (popup)  Display Help   
smiley cool  smiley wink  smiley biggrin  smiley smile  smiley frown  smiley eek  smiley mad  smiley confused  smiley rolleyes  smiley tongue  smiley cry 
Captcha reload
Copy the text:


 
 
^ Top ^