[blitz] - is there a max size of a NEW TYPE ?

peceha · 21 March 2021, 10:19

Hi,
i'm asking because the program I've been writing has a problem

whenever I need to prepare next level I clear all necessary list using

Code:

ClearList itm()
ClearList ent()

and so on.

The ent() list is .ENTITY type which is quite big (the type, not the list) and near the and there are many (around 7 individual and 10 as a table) pointers to .ITEM type from the itm() list

If I let the blitz clear the lists (the code above) then some trash remains and the .ITEM pointers inside .ENTITY keep some data from previous level (like \name.s field for example)

When I manually set to zero all .ITEM pointers inside .ENTITY and then kill .ENTITY entry for the whole list the problem is gone (just KillItem ent() doesnt solve the problem, have to zero all .ITEM pointers myself)

So maybe there is a limit for a new type and blitz just ignores whenever something is beyond it (when clearing) ...

Thanks

-----------------------------------
EDIT
-----------------------------------
could be I'm wrong about my assumption about the size
investigating little bit more now and there is a chance a problem is somewhere else

peceha · 22 March 2021, 09:50

Looks like I always should first (within a new type) set to zero all the pointers to other new types (if they are on separate list/table) and then I can safely do KillItem() or ClearList.
If I won't clear these pointers before removing an item than strange things happen.

E-Penguin · 10 April 2021, 20:56

It sounds reasonable to do a "deep delete" yourself - BB2 won't follow the pointers

21 March 2021, 10:19	#1
peceha Registered User Join Date: Dec 2017 Location: Poland Age: 47 Posts: 282	[blitz] - is there a max size of a NEW TYPE ? Hi, i'm asking because the program I've been writing has a problem whenever I need to prepare next level I clear all necessary list using Code: ClearList itm() ClearList ent() and so on. The ent() list is .ENTITY type which is quite big (the type, not the list) and near the and there are many (around 7 individual and 10 as a table) pointers to .ITEM type from the itm() list If I let the blitz clear the lists (the code above) then some trash remains and the .ITEM pointers inside .ENTITY keep some data from previous level (like \name.s field for example) When I manually set to zero all .ITEM pointers inside .ENTITY and then kill .ENTITY entry for the whole list the problem is gone (just KillItem ent() doesnt solve the problem, have to zero all .ITEM pointers myself) So maybe there is a limit for a new type and blitz just ignores whenever something is beyond it (when clearing) ... Thanks ----------------------------------- EDIT ----------------------------------- could be I'm wrong about my assumption about the size investigating little bit more now and there is a chance a problem is somewhere else Last edited by peceha; 21 March 2021 at 10:59.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Max HD size usable with SurfSquirrel?	Doc Mindie	support.Hardware	12	12 April 2013 10:42
OS 3.5 Max HD Size	TheCorfiot	support.Hardware	19	01 April 2009 11:50
Max size for 1.3 HDF?	Jherek Carnelia	support.Other	7	08 May 2007 07:21
MAX size HD with rom 3.1	Stormrider	support.Hardware	1	04 March 2006 14:00
Avatars max size goes down to 64*64	RCK	project.EAB	6	08 January 2002 00:13

22 March 2021, 09:50	#2
peceha Registered User Join Date: Dec 2017 Location: Poland Age: 47 Posts: 282	Looks like I always should first (within a new type) set to zero all the pointers to other new types (if they are on separate list/table) and then I can safely do KillItem() or ClearList. If I won't clear these pointers before removing an item than strange things happen.

10 April 2021, 20:56	#3
E-Penguin Banana Join Date: Jul 2016 Location: Darmstadt Posts: 1,213	It sounds reasonable to do a "deep delete" yourself - BB2 won't follow the pointers

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)