|
Post by George on Apr 3, 2022 10:50:26 GMT -5
Robert: Yeah, similar, but the eye exam I had a couple weeks ago said my cataracts were'nt bad enough to warrant it yet.
George
|
|
|
Post by George on Apr 3, 2022 13:45:19 GMT -5
Robert: My eye guy said the best way to tell if your cataracts are at the surgery point, is driving at night. He said when you start seeing star spikes/halos around streetlights, it's time.
When he does an exam he also takes those internal detailed photos of the inside of the eyeball. He has now a series of them for me taken over the last 10-15 years. And he can actually show me the cataract progression over the years. Still not too bad in the photos, which jives with my night vision.
It's fascinating to see Linda's photos, which show the macular degeneration in spectacular fashion. There's the back of the eyeball, with these clusters of black patches right in the middle - the dead macular cells. And nothing can be done - sad.
George
|
|
|
Post by George on Apr 3, 2022 14:45:40 GMT -5
Well, all my friends, and Linda, who has also had the surgery, have all said it went well and was a major improvement. I know when my eyes get there, I'll jump at it.
George
|
|
|
Post by George on Apr 4, 2022 15:09:59 GMT -5
Gbl Macros.doc (35 KB) Stefan: Robert: OK, Using Stefan's initial Gbl Intro documentation, I've massaged it into what might be suitable for addition to the Help file Macros section as "Working with Global Data". I haven't added any samples etc. simply because I felt that anyone even exploring this area of macros had to be reasonably proficient, and would just need some basic guidance. George
|
|
|
Post by Stefan on Apr 6, 2022 6:39:12 GMT -5
George, I think(!!!!) the GBL storage works as follows....
(1) You offer the user a concept of 'one or more tables, each of which is identified by a table number'. (2) In the internal representation, each such logical 'table' maps onto two separate array-like structures, one for 'strings' and one for 'numerics'.
(3) Entries are saved in these internal structures using three fields: 'table number', 'label/key-str' and 'value'. This would allow all the functions and searches you provide and the necessary serial and direct accesses to data.
(4) The user simply deploys the appropriate ...GBL_NUM or ...GBL_STR function and the internal complexity is hidden from them.
I think when the document mentions sub-tables in various places, it describes some of the underlying structures.
That is what's quite confusing and pretty much irrelevant to the user.
I attach a revision of the proposed document, suggesting some minor changes. I hope this helps. Just apply the changes you like and the doc should shrink back to it's inital size.
SN Gbl Macros.doc (56 KB)
|
|
|
Post by Stefan on Apr 7, 2022 3:07:33 GMT -5
George,
If you haven't already looked at the previous revision of the document....
This is newer. I realised that the naming differences between LABEL and NAME$ in the functions need not exist.
Just use NAME instead of LABEL or KEY-STR, etc everywhere.
This is the revised doc.
|
|
|
Post by George on Apr 7, 2022 8:20:40 GMT -5
Stefan: Thanks, anything to simplify this is welcome.
George
|
|