Skin Framework - Problems with Combit List&Label

Problems with Combit List&Label

Printed From: Codejock Forums
Category: Codejock Products
Forum Name: Skin Framework
Forum Description: Topics Related to Codejock Skin Framework
URL: http://forum.codejock.com/forum_posts.asp?TID=8920
Printed Date: 14 May 2024 at 6:57pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: Problems with Combit List&Label

Posted By: Herbert Lackner
Subject: Problems with Combit List&Label
Date Posted: 27 November 2007 at 9:47am

Hi Folks,

we're using Combit List & Label Ver. 12 as Report Generator. There is quite a strange behaviour when printing a report: The "Printer Dialog" Window is shown with a standard Windows XP Border for about 3 seconds, then it disappears. After starting the printout the progress window is shown with a default XP Border wich also disappears after a few seconds. The "Preview Window" is ok, but the "Designer Window" is an awfull mess of showing/not showing/disappearing and thus flickering Window Borders.

Anybody working with List&Label and SkinFramework?

How can I prevent List&Label from being "frameworked"?

Ah, yes, forgot to mention: We are not using the List&Label OXC but calling the DLLs directly.

Any answers are mostly appreciated!

Thanks in advance

Herbert Lackner

Replies:

Posted By: Oleg
Date Posted: 27 November 2007 at 10:13am

Hi,

It will be great if you attach sample to show what you do.

-------------
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS

Posted By: Herbert Lackner
Date Posted: 27 November 2007 at 10:51am

Hi Oleg,

thanks for your quick reply.

Here is a recording of my application and "misbehaving" List&Label:

https://forum.codejock.com/uploads/20071127_105138_ListLabelSkinFr.zip - uploads/20071127_105138_ListLabelSkinFr.zip

Thanks,

Herbert

Posted By: Oleg
Date Posted: 27 November 2007 at 11:56am

Hello,

Thanks, I will download eval version to check.

-------------
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS

Posted By: Herbert Lackner
Date Posted: 28 November 2007 at 2:35am

Hi Oleg,

that's great!

http://www.combit.de - www.combit.de

Thats the way we use it:


  hJob = LlJobOpen(CMBTLANG_GERMAN)
  LlSetDlgboxMode LL_DLGBOXMODE_NOBITMAPS
  ret = LlSetOption(hJob, LL_OPTION_NEWEXPRESSIONS, 1)
  ret = LlSetOption(hJob, LL_OPTION_MULTIPLETABLELINES, 1)
  ret = LlSetOption(hJob, LL_OPTION_SUPPORTPAGEBREAK, 0)
  ret = LlSetOption(hJob, LL_OPTION_SORTVARIABLES, 1)
  ret = LlSetOption(hJob, LL_OPTION_DRAWFOOTERLINEONPRINT, 1)
  ret = LlSetOption(hJob, LL_OPTION_COMPRESSSTORAGE, 0)
  ret = LlSetOption(hJob, LL_OPTION_NOPARAMETERCHECK, 1) 
  ret = LlSetOption(hJob, LL_OPTION_XLATVARNAMES, 0) 
  ret = LlSetOption(hJob, LL_OPTION_CONVERTCRLF, 1)
  ret = LlPreviewSetTempPath(hJob, AppPath)

  Call LlDefineFieldStart(hJob)
  Call LlDefineVariableStart(hJob)

  'define some Fields and some Variables
  'Fields are used in Tables
  'Variables ase used in Textboxes etc.
 
  LlDefineFieldExt(hJob, "aNumericValue", 200, LL_NUMERIC, "")

  LlDefineField(hJob, "aTextValue", " ")
 
  LlDefineVariableExt hJob, "TextVariable", "", LL_TEXT, ""

  'Start printing 
  ret = LlPrintWithBoxStart(hJob, LL_PROJECT_LIST, "ObjName", LL_PRINT_USERSELECT Or LL_PRINT_MULTIPLE_JOBS, LL_BOXTYPE_NORMALMETER, me.hwnd, "Title")
 
  LlPrint hJob
 
  'Start printing...

  LlDefineFieldExt(hJob, "aNumericValue", 1.56, LL_NUMERIC, "")

  LlDefineField(hJob, "aTextValue", "This is the printed Text...")
 
  LlDefineVariableExt hJob, "TextVariable", "This is the Value", LL_TEXT, ""

  While LlPrintFieldsEnd(hJob) = LL_WRN_REPEAT_DATA
  Wend

  ret = LlPrintEnd(hJob, 0)

Just to show you how List&Label is used by us. There are some Examples in the Evaluation Version, but most of them use the ocx...

Thanks

Herbert

Posted By: Herbert Lackner
Date Posted: 13 December 2007 at 2:42am

Hi Oleg,

any news on this one? Any news would be really appreciated!

thanks

Herbert

Posted By: Herbert Lackner
Date Posted: 03 January 2008 at 7:19am

Hi Oleg,

sorry, but I have to bring this one up again. We have to roll out our yearly update and there ist still no solution to our problem!

thanks

Herbert

Posted By: Oleg
Date Posted: 03 January 2008 at 11:24am

Hi,

In november I registered in combit to get link to eval download, but they didn't answer :-(

Will try again.

-------------
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS

Posted By: Oleg
Date Posted: 04 January 2008 at 3:16am

Hi,

I downloaded it, tried in 2 samples and this print setup dialog looks fine for me...

Do you have last SkinFamework ? Can you try insert it in some sample and check how it works with samples ?

-------------
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS

Posted By: Dongolo
Date Posted: 16 January 2008 at 6:16am

Hi Herbert,

do you have any full example of using List & Label API in Visual Basic 6 with out the LL control (OCX)?

I use to make reports only the OCX.

I need your help, please.

Thank you in advance

dong

Posted By: Dongolo
Date Posted: 16 January 2008 at 12:08pm

Hi all,

can any one of you give me an example of using List & Label API in Visual Basic 6 with out the LL control (OCX)?

I use to make reports only with the OCX.

I need your help, please.

Thank you in advance

dong

Posted By: Oleg
Date Posted: 17 January 2008 at 2:32am

Hello, dong

Think its not right forum for this question. Ask in combit.de.

-------------
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS

Posted By: Herbert Lackner
Date Posted: 19 January 2008 at 11:16am

Hi Oleg,

SkinFramework Version is 11.2.0.0. How do I update?

Thanks,

Herbert

Posted By: Herbert Lackner
Date Posted: 19 January 2008 at 11:39am

Hi Oleg,

just downloaded the current evaluation version of SkinFramework, inserted it into an LL12 Example - still: the Designer is not working 100% (the menu line is hidden and only navigable by keystoke Alt+letter)...

thanks

Herbert

Posted By: Herbert Lackner
Date Posted: 19 January 2008 at 11:47am

OK, so I found a solution:

in the initialisation of my printing class I set

fMainForm.SkinFramework.AutoApplyNewWindows = false

and when terminating the class

fMainForm.SkinFramework.AutoApplyNewWindows = true

That works for me - one little glitch stays: the new windows inherits some Colors from the Framework... but that doesn't matter...

thanks

Herbert