Any chance for pointers in VB?

  • Thread starter Thread starter Crirus
  • Start date Start date
* "Fergus Cooney said:
I look forward to the table-top screen/graphics tablet - 100cm x 100cm,
120dpi. That's 90MB just for the desktop background image!! ;-))

ROFL
 
Hi Armin,
I fully agree. That has always been the most stupid solution I did hear.
Hardware developers making computers faster and lousy software developers
making programs slower. So the benefit is zero.
:-)
Cor
 
* "Armin Zingler said:
Software developers who think this way are responsible for the need of
faster computers.

ACK. Hardware isn't fast enough for high-level programming yet.
 
* "Cor said:
I fully agree. That has always been the most stupid solution I did hear.
Hardware developers making computers faster and lousy software developers
making programs slower. So the benefit is zero.

I set up Windows 3.11 on my new machine and it takes less than 1 second
to start...

I think computers are not fast enough. When Circus is asking for
pointers because of performance problems, he will have to use a
low-level programming concept. That's really bad. If computers were
faster, image processing in VB.NET would be no problem.
 
Hi Herfried,

I follow this thread half and half, soon I need your knowledge, because I
think I am going to do something with bitmaps. (I need maybe a lot of links
and your knowledge).

When it is so far, I tell you and I am sure you will help me, but now I look
with a half eye to this thread.

First of all, I don't believe that C# has really hard memory pointers. I
think it has relative memory pointers. Hard memory pointers where on
mainframe in the very past and came back with the microcomputer. But every
builder of an OS would try to avoid them.
But I don't know enough from C# to say that while being sure, it is just a
guess.
So I am curious if my guess is right?

It always has been, with this speed thing, is that the generic modules for
doing this kind of things are ready when a format is generalised. Looking to
pictures formats now it is for me hash.

But that has been with all things with computers in past. Who ask here for a
WP format question, while in the past that was a very normal format?

And of course you still need speed for the amount of data in a bitmap, but
that has in my eyes nothing to do with pointers.

This became a long message, more for the night for you I think?

Cor
 
Good morning Cor,

What's a 'hard' pointer? And does that imply some sort of 'soft' pointer?

Regards,
Fergus
 
Dmitriy Lapshin, not that I like the ideea to add a imageList just for this
multilevel transparency I need, but can you be more specific?


Dmitriy Lapshin said:
Hi,

The ImageList class can blit bitmaps with transparency with its Draw method.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

Crirus said:
No one on Drawing newsgroup had an answer if there is a BitBlt-like method
or a workaround it in GDI+...using a mask for transparence layer.... without
direct memory access and lock
 
The only thing I can do right now is to draw the bitmaps pixel by pixel and
calculate the alpha myself from the mask color
I have to draw about 20x14=280 images. Each image has 80 X 80 pixels
 
Hi Fergus,
Maybe that is my name for it, that I did use by instance in far past to make
a branch to memory adress zero. (null booting of the computer).
Cor
 
Hi Cor,

Lol. I know that one too! ;-)

I'm not worried about whether the term is correct - I want to know what
<you> mean by it. I'm curious as to what distinction you are making, and this
will help me answer your question about pointers in C#.

[...pause for thought...re-reads the posts...]

I think I've got it, though - you mean a specific address, such as 0000
for the reboot (wasn't there another one at 0080 for a 'soft' reboot,
perhaps). If that's a 'hard' pointer, then a 'soft' pointer would be one
relative to the process' memory space (and translated to a hard address by the
CPU and its associates).

Yes, C# uses soft pointers. But these are as valid for the process as if
they were hard. In order to use them the C# programmer has to 'fix' the object
in memory so that the Garbage Collector will not move it. The address is then
as hard as it gets for a process - direct access to the memory of the object.

For Crirus, then, that will be the bits of the bitmap. For someone else,
it may be the bytes of some structure.

Regards,
Fergus
 
Hi Fergus,

That is what I thought.

When someone says C# has the posibility to point to a memory adress, I
always think does he know what he says.

Normaly with modern operating systems you cannot do anything with that
because of the relocating in memory of processes ( I don't know if NT does
that but I asume that it happens when the garbadge is cleaned).

Thank you.

Cor
 
Hey,

there is some kind of a reward for the longest post launched? :D

Crirus

P.S. No need to answer
 
Hi Crirus,

But I'm going to answer anyway, lol.

We had a very long thread with over 100 (wow!!) posts in it a while back.
There was excitement and wonder at the length.

I went Googling and discovered that we were short of the record by a mere
few thousand.

Ah well. ;-))

Regards,
Fergus
 
* "Cor said:
I follow this thread half and half, soon I need your knowledge, because I
think I am going to do something with bitmaps. (I need maybe a lot of links
and your knowledge).

Didn't you receive the brainconnector yet?
First of all, I don't believe that C# has really hard memory pointers. I
think it has relative memory pointers. Hard memory pointers where on
mainframe in the very past and came back with the microcomputer. But every
builder of an OS would try to avoid them.
But I don't know enough from C# to say that while being sure, it is just a
guess.
So I am curious if my guess is right?

Sorry, I never used 'unsafe' blocks with C# (as a high-level programmer
I never needed them).
 
Hi Herfried,

!! Didn't you receive the brainconnector yet?

ROFL.

!! Sorry, I never used 'unsafe' blocks with C# (as a
!! high-level programmer I never needed them).

Oooh, isn't <he> the high and mighty one, then. Wouldn't want to soil his
hands on bits and bytes, wouldn't want to go near those nasty pointer things.

Regards,
Fergus
 
Hi Fergus,

I had an other answer, stuffed it because this one is better.

We both have done a lot on memory level programming I think.

But we both have seen, that when the computers where changing, the first
programs which where useless where those with hard (or even virtual)
pointers in it.

Cor
 
Hi Herfried,

I think that my brainconnector works better and better. But there is till
now no connector on bitmaps.

Cor
 
Hi Cor,

For sure, hard-coded <anything> can limit the life span. But, sadly, many
well-designed, generically coded, super flexible, etc, etc, programs have
similarly fallen to the wayside because of moving times.

RAD - Rapid Application Development :-))

RAD - Rapid Application Disuse :-((

Regards,
Fergus
 
Back
Top