In the latest beta version of newlib the ctype.h file has "(_ctype_+1)" instead of "__ctype_ptr" in this code so it should be working correctly.
I changed this about a year ago according to an old bugzilla report.
Search found 488 matches
- Sat Jun 17, 2017 7:13 pm
- Forum: SDK Support
- Topic: Bug in newlib/include/ctype.h with vbcc
- Replies: 1
- Views: 3955
- Fri Apr 21, 2017 6:24 pm
- Forum: General AmigaOS
- Topic: ARexx "not not" bug
- Replies: 24
- Views: 15403
Re: ARexx "not not" bug
Actually "!!value" does work in C and is commonly used to normalize arbitrary zero/non-zero boolean values into being either 0 or 1 for false and true respectively.broadblues wrote: Fairly sure the same would work in C (!! expression) would give an error. !(! expression) would work.
- Sat Feb 11, 2017 6:25 pm
- Forum: SDK Support
- Topic: LoadSeg() or VERSION command crash with corrupted binary
- Replies: 3
- Views: 6118
Re: LoadSeg() or VERSION command crash with corrupted binary
You could just scan the file contents for the "$VER:" sequence that starts the version tag.
- Tue Jan 10, 2017 11:12 am
- Forum: General Developer Support
- Topic: Rubber banding/bounding box selection
- Replies: 5
- Views: 2473
Re: Rubber banding/bounding box selection
@chris
You should read up on the LockScreen() and UnlockScreen() functions in the intuition.library autodoc. They are made specifically for this purpose.
You should read up on the LockScreen() and UnlockScreen() functions in the intuition.library autodoc. They are made specifically for this purpose.
- Wed Jan 04, 2017 7:46 am
- Forum: AmigaOS Feature Requests
- Topic: DTM_WRITE feature requests
- Replies: 26
- Views: 36510
Re: DTM_WRITE feature requests
Yes, it does look like the wrong version was included in the update.
Versions 54.4 to 54.6 had a bug in the DTST_RAM handling but this was fixed in version 54.7 which was supposed to be the version shipped with 4.1 FE update 1.
Versions 54.4 to 54.6 had a bug in the DTST_RAM handling but this was fixed in version 54.7 which was supposed to be the version shipped with 4.1 FE update 1.
- Sat Dec 17, 2016 7:53 pm
- Forum: General AmigaOS
- Topic: Unexpected shell behavior?
- Replies: 10
- Views: 4249
Re: Unexpected shell behavior?
Just type the command "path" and you will get a list of the directories that are searched for commands. Most likely APPDIR: is one of them and if so that is what is causing the behaviour.
- Tue Nov 22, 2016 9:28 am
- Forum: General Developer Support
- Topic: GADGETUP message missing if gadget is in sub layout
- Replies: 10
- Views: 7632
Re: GADGETUP message missing if gadget is in sub layout
Try setting LAYOUT_DeferLayout to TRUE on the root layout.
If it helps then I think I know what the problem is and how to fix it.
If it helps then I think I know what the problem is and how to fix it.
- Mon Nov 21, 2016 4:27 pm
- Forum: General Developer Support
- Topic: GADGETUP message missing if gadget is in sub layout
- Replies: 10
- Views: 7632
Re: GADGETUP message missing if gadget is in sub layout
GACT_RELVERIFY I think you mean GA_RelVerify. Setting GA_RelVerify to TRUE sets the GACT_RELVERIFY flag in the gadget->Activation field, setting GA_RelVerify to FALSE clears it. it applies to GM_HANDLESCROLL Yes, I mentioned mouse wheel in the first post. Have you added some debug code to ensure th...
- Mon Nov 21, 2016 10:04 am
- Forum: General Developer Support
- Topic: GADGETUP message missing if gadget is in sub layout
- Replies: 10
- Views: 7632
Re: GADGETUP message missing if gadget is in sub layout
From conversations on this subject held in email I should point out that the significant piece of information missing from this request for help is that it applies to GM_HANDLESCROLL not GM_HANDLEINPUT The GM_HANDLESCROLL method isn't documented in any of the autodocs but it looks like the requirem...
- Mon Nov 21, 2016 9:44 am
- Forum: General Developer Support
- Topic: GADGETUP message missing if gadget is in sub layout
- Replies: 10
- Views: 7632
Re: GADGETUP message missing if gadget is in sub layout
So how do I implement it in my class to get this working ? Like I said WMHI_GADGETUP never arrives. You implement GM_HITTEST, GM_GOACTIVE, GM_HANDLEINPUT and GM_GOINACTIVE as usual. The IDCMP_IDCMPUPDATE notification is done by layout.gadget in its input handler. Your gadget gadget should also have...