Kilotecs Software Corner

Fair enough, I'd try it on your Jornada 680 or 690 and check to see what happens there in the meantime.
Enjoy your bath!





Attachments
----------------
treat-yo-self.jpg (47KB - 0 downloads)

I will. the error must be somewhere.

haha Thank you

Correct, the SCL is designed for HVGA, VGA get shrunk down rather small.

Ok thank you C, then I will take them of my device

Yeah on some of the screenshots I helped you with when I used my CE thin client, I cropped them down to 640x240 HVGA so the SCL listings look neater. Obviously I didn’t do a 100% amazing job at the crop but it gets the point across.

Your wider issues highlight why constantly reinstalling runtimes is a bad idea. It would appear that there is a wider issue in the .vb, but regsrving DLL's over and over unecessarily just risks corrupting the registry. MS really screwed up with the deployment for .VB's. They eventually learnt with .net: you handle the runtime and the rest works itself out.

OK I can understand that. But I haven't installed any more runtimes. I always said no during installation.
Maybe my device got too much with the constantly new apps from me.
Oh it's annoying. Tomorrow is a new day so I'll see what I can do.

Oh. Other than your very first apps, I don’t use the cab file installers you have at all. I always just extract the cab and grab the .vb file and its support files.

I will say if you’re installing cabs and uninstalling vb programs too it has a tendency to mess everything up. Another reason I like the runtime less installers or the raw vb file

that is very interesting. I never expected that. is this a CE problem? for the user from whom you should ask the least, the installation files are of course great.

ok that means if I already have a VB program installed I don't really need to install the next one? although I deny the runtime installations? the user would then have to install the runtimes and extract the program individually. is of course expensive.

In an ideal world - eventually, you should get your cab files to be like this program:
https://www.hpcfactor.com/scl/1/Alpaxo_Software/Quackenchat/version_...
The cab would be "CEF", meaning install without regard to architecture for CPU
I extracted the cab and this is all it does:

Files	Order Number	Flags	ID Dir	FileName in CAB	FileName 
 

001	001	0x00000000	 \Program Files\Quackenchat	QUACKE~1.001	"Quackenchat.vb" 

002	002	0x00000000	 \Program Files\Quackenchat	QUACKE~1.002	"Quackenchat.bmp" 

003	003	0x00000000	 \Program Files\Quackenchat	QUACKE~1.003	"Quackenchat.wav" 

 

*****************************************************************************************************************************************************************	  

 

ID S.	Shortcut Name	Installed at	Points to 

 

001	Quackenchat.lnk	\Windows\Start Menu\Programs	"Quackenchat.vb"

Installs those top three, then links the .vb into the start menu.

Then it's up to user to install the runtime, since different CE versions have different runtimes. That's why C:Amie made that new Visual Runtime 2.0 thingie

Edited by torch 2023-02-06 9:15 PM

So I only need the .vb file and of course things like sounds and pictures? Ok...easy. but I dont k ow what happens when files are saved in the app. Trying to save to the app.path. there is no known app path then when it is not installed. Mhh... I will try this tomorrow.
Then, of course, it is important to link the runtimes in the SCL entry or make a big hint that the user k ows what to do.

True, C:Amie and I are working on making sure every single VB program has a way for the user to be informed where/how to download the runtimes.

Make sure when you do build your cab to mark it "CEF"

Basically, I think all you have to do is build a cab as "CEF" and select no to installing the runtimes - I don't think you'd need to change anything else?

And again, I'm never intending to criticize or rush you, I just like to offer suggestions where I can so I can hope to assist for future efforts.

So, today I copied all .dll I needed for the app to the windows folder because the app need some of the dll. Or better said, O had these dll still in my windows folder because of the other apps. Then I started only the .vb file from my CF card.
Same here, hourglass and nothing happend.
There must be something wrong with the .vb file

Edited by Citgo 2023-02-07 7:08 AM

I guess I found the problem!
There's a variable for the background color of the forms.
When the app starts, the variable is queried and the background color for all shapes is set accordingly. This works in the emulator without delay. The program freezes on the device and the hourglass appears. So there was no problem with the runtimes being internal. I still don't understand why.

Ok...everything works fine now.
The problem was a sub function. Don't know why but...ah... now it works
Next app is coming. Will take some screenshots today.
It's an app which I will also use by myself.