-
Jeffrey Lee authored
Detail: s/Module, hdr/VFPSupport - New/changed features: - Contexts can now be flagged as being in application space if they're created with the VFPSupport_Context_AppSpace flag - VFPSupport_ChangeContext accepts a VFPSupport_ChangeContext_AppSpace flag, which will force the context change to occur in a nonlazy manner if the currently active context is in application space - VFPSupport_CreateContext accepts a VFPSupport_CreateContext_LazyActivate flag, to indicate that after creation the context should be activated lazily (unlike VFSupport_CreateContext_Activate) - VFPSupport_Context_Activate renamed to VFPSupport_CreateContext_Activate for clarity - VFPSupport_CheckContext now ignores the Activate/LazyActivate flags, so the same flag word can be passed to Check & Create - "Context ID" simplified to just "Context pointer", as an indiciation of the fact that I now have no plans to make VFPSupport keep a master list of extant contexts - This makes it legal for programs to move/copy/delete contexts as long as they've made sure that the ExamineContext doesn't indicate that any part of the context is active - VFPSupport_ExamineContext now returns the context size in R4 instead of the context ID Test/test1,ffb - Updated to work with new API Admin: Tested on rev A2 BB-xM. VFPSupport_ExamineContext change is backwards-incompatible! Version 0.02. Tagged as 'VFPSupport-0_02'
1355ea60