Page 2 of 2

Re: A Personal *Event Coundown Reminder* (Feedback Welcome)

Posted: Sun Oct 06, 2024 4:51 pm
by Paul
Randy Walker wrote: Sun Oct 06, 2024 3:42 pm Is it a bug or something I did wrong? I'm pretty good at that :oops:
It's you :D

If you follow the changes made to latest versions of PB and follow the forum, you will try changing all types of ".l" to ".i" and the code will then work.

Re: A Personal *Event Coundown Reminder* (Feedback Welcome)

Posted: Sun Oct 06, 2024 5:04 pm
by Randy Walker
Paul wrote: Sun Oct 06, 2024 4:51 pm
It's you :D

If you follow the changes made to latest versions of PB and follow the forum, you will try changing all types of ".l" to ".i" and the code will then work.
You are soo correct. It was me. :oops:
Just another I/O error
I never claimed I was a programmer.
Also never claimed I wasn't an Idiot/Operator. :)

Thank you for setting me straight Paul!!

Re: A Personal *Event Coundown Reminder* (Feedback Welcome)

Posted: Tue Oct 08, 2024 3:09 pm
by Axolotl
Hi Randy,

some brief suggestions for you next housekeeping task :oops:
Randy Walker wrote: Sun Oct 06, 2024 5:04 pm .....I never claimed I was a programmer. .....
1. I prefer using constants like #WND_Main, #GDT_btnAddNewEvent, #GDT_DiscardEvent, #GDT_DiscardAllChanges, etc.
Why? Because I have the feeling, it makes the code more readable and understandable (especially after a while)

Code: Select all

Enumeration EWindow 1 
  #WND_Main 
  ; tbc. 
EndEnumeration

Enumeration EGadget 1 
  #GDT_btnAddNewEvent 
  #GDT_DiscardEvent 
  #GDT_DiscardAllChanges 
  ; tbc. 
EndEnumeration
2. Important for 64-bit apps is the use of SetWindowLongPtr_() instead of SetWindowLong_(). Same applies to SetClassLong_()
Why? See MSDN:
Note This function has been superseded by the SetWindowLongPtr function. To write code that is compatible with both 32-bit and 64-bit versions of Windows, use the SetWindowLongPtr function.

Re: A Personal *Event Coundown Reminder* (Feedback Welcome)

Posted: Tue Oct 08, 2024 9:25 pm
by Randy Walker
Axolotl wrote: Tue Oct 08, 2024 3:09 pm Hi Randy,

some brief suggestions for you next housekeeping task :oops:
Randy Walker wrote: Sun Oct 06, 2024 5:04 pm .....I never claimed I was a programmer. .....
1. I prefer using constants like #WND_Main, #GDT_btnAddNewEvent, #GDT_DiscardEvent, #GDT_DiscardAllChanges, etc.
Why? Because I have the feeling, it makes the code more readable and understandable (especially after a while)

2. Important for 64-bit apps is the use of SetWindowLongPtr_() instead of SetWindowLong_(). Same applies to SetClassLong_()
Why? See MSDN:
Note This function has been superseded by the SetWindowLongPtr function. To write code that is compatible with both 32-bit and 64-bit versions of Windows, use the SetWindowLongPtr function.
Good suggestions Axolotl, Thanks! Will try to research that SetWindowLongPtr function for a way to adapt. Structures are always a big challenge for me. :oops:

Re: A Personal *Event Coundown Reminder* (Feedback Welcome)

Posted: Sat Nov 09, 2024 6:50 pm
by Randy Walker
oryaaaaa wrote: Sat Jan 28, 2012 3:03 pm I tested your app.

Japanese cell phone event remider
  • 2 month calender displayed
  • Please select event, holiday or aniversery?
  • 1.Icon Select
  • 2.day and night?
  • 3.start time/day
  • 4.finish time/day
  • 5.repeat? (day, week, monthry, year)
  • 6.Alarm ( annouce, prepare announce, off)
  • 7.Alarm sound ( FullSong/Melody, Music, Movie, OFF)
  • 8.event detail
Don't care about all that Garbage. :evil: Just a bunch of garbage to complicate a very simple thing.