wix - ICE03: String overflow (greater than length permitted in column); Table: CustomAction -


i getting ice03: string overflow warning following code:

<customaction id="customactionid"           return="check"           property="someproperty"           value="very long string comes here"           execute="immediate"/>

this code included in separate .wxs file in fragment. if include directly within "product" tag warning disappears. happens following code:

<binary id="somebinarywithaverylongname" sourcefile="sourcefile" />

i find out why happening?

the customaction/@value attribute has limit of 255 characters in windows installer. so, if "very long string comes here" has more 255 characters hitting ice warning. binary/@id shorter because "identifiers" in msi , windows installer standardized on 72 characters identifiers.

it mystery why ice03warning message different when placed under product element because ice validation executed against final msi. final msi not care how organized .wxs source code build msi. possible seeing other warnings (not ice03) based on whether code in product or under fragment?

the reason ask difference between product or fragment because compiler knows different things when compiling product section vs. fragment section. compiler knows product section creating .msi file. fragment on other hand creating .msi file, .msm file, or .msp file. .msm , .msp files have additional restrictions beyond .msi file.

for example, when building .msm file of identifiers suffixed module/@id. adds additional 37 characters identifiers limited 72 characters. binary/@id further limited because ends being name of stream in .msm file , can't go on around 60 chars.

anyway, net result when in fragment compiler applies possible rules identifiers. rules may more restrictive absolutely necessary in cases. if heed warnings/errors code should compile in cases.


Comments

Post a Comment

Popular posts from this blog

linux - xterm copying to CLIPBOARD using copy-selection causes automatic updating of CLIPBOARD upon mouse selection -

i've tried various ways coerce xterm (versions 285 , 292) copy selection clipboard clipboard whenever press ctrl-shift-c. promising way far has been, in ~/.xresources, put this: xterm*vt100.translations: #override \ ctrl shift <keypress> c: copy-selection(clipboard) \n\ ctrl shift <keypress> v: insert-selection(clipboard) ctrl-shift-v works perfectly, copying has nuance... if restart xterm, highlighting text puts things in primary clipboard; expected, proper, default behavior. if hit ctrl-shift-c, copies current selection clipboard clipboard. the bug, however, if highlight text after first time pressed ctrl-shift-c, you'll see highlighting copies both primary and clipboard. cannot figure out how stop xterm updating clipboard upon selection... , doesn't make sense me in first place. i said, @ specific point in time, copy selection clipboard... yet starts updating automatically upon selection after doing once... anyone have workaround...
Read more

c++ - qgraphicsview horizontal scrolling always has a vertical delta -

Image
i've subclassed qgraphicsview custom canvas used in cad application. i've reimplemented qgraphicsview::wheelevent check keyboard modifiers control key and, if control key pressed, zoom. i'm trying implement horizontal scroll when user holds shift , uses wheel. the problem i'm having horizontal scrolling always scrolls 0.279. not huge problem, hugely annoying , points else being wrong. so, here questions: is right way implement horizontal scrolling? if not, is? how eliminate delta of 0.279? thanks in advance. code , sample output below void myview::zoom(int delta) { double factor = pow(1.2, delta/abs(delta)); this->scale(factor, factor); } void myview::scrollhorizontal(int level) { qpointf center = maptoscene(viewport()->rect().center()); qdebug() << "center: " << center.x() << ", " << center.y(); centeron(qpointf(center.x() - level, center.y())); } void myview::wheelevent(qwheeleve...
Read more